check-contribution
Validates operator chart contribution practices (helm template, ct lint, docs generation, version bump) before committing changes.
Best use case
check-contribution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validates operator chart contribution practices (helm template, ct lint, docs generation, version bump) before committing changes.
Teams using check-contribution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/check-contribution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How check-contribution Compares
| Feature / Agent | check-contribution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validates operator chart contribution practices (helm template, ct lint, docs generation, version bump) before committing changes.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Check Operator Chart Contribution Practices Verify that all contribution guidelines from `deploy/charts/operator/CONTRIBUTING.md` are followed before committing Helm chart changes. Do not make any edits to files. ## Checks ### 1. Helm Template Validation ```bash cd "$(git rev-parse --show-toplevel)"/deploy/charts/operator && helm template test . ``` Verify the output contains valid Kubernetes YAML without errors. ### 2. Chart Linting ```bash ct lint ``` Report any linting errors or warnings. ### 3. Documentation Generation ```bash helm-docs --dry-run ``` Verify that `values.yaml` variables are documented and the generated README.md matches. ### 4. Chart Version Bump If chart files changed, verify: - `deploy/charts/operator/Chart.yaml` version is bumped for operator changes - `deploy/charts/operator-crds/Chart.yaml` version is bumped for CRD changes - Version follows [SemVer](https://semver.org/) and bump type matches the change scope ## Output Format ``` ✅ or ❌ Helm template renders successfully ✅ or ❌ Chart linting passes ✅ or ❌ Documentation up-to-date ✅ or ❌ Chart version bumped appropriately ``` Include specific errors for any failing checks with actionable remediation commands.
Related Skills
split-pr
Analyzes current changes and suggests how to split them into smaller, reviewable PRs
vmcp-review
Reviews vMCP code changes for known anti-patterns that make the codebase harder to understand or more brittle. Use when reviewing PRs, planning features, or refactoring vMCP code.
toolhive-cli-user
Guide for using ToolHive CLI (thv) to run and manage MCP servers and skills. Use when running, listing, stopping, building, or configuring MCP servers locally. Covers server lifecycle, registry browsing, secrets management, client registration, groups, container builds, exports, permissions, network isolation, authentication, and skill management (install, uninstall, list, info, build, push, validate). NOT for Kubernetes operator usage or ToolHive development/contributing.
code-review-assist
Augments human code review by summarizing changes, surfacing key review questions, assessing test coverage, and identifying low-risk sections. Use when reviewing a diff, PR, or code snippet as a senior review partner.
deploy-otel
Deploy the OpenTelemetry observability stack (Prometheus, Grafana, OTEL Collector) to a Kind cluster for testing toolhive telemetry. Use when you need to set up monitoring, metrics collection, or observability infrastructure.
doc-review
Reviews documentation for factual accuracy
pr-review
Submit inline review comments to GitHub PRs and reply to/resolve review threads using the GitHub CLI and GraphQL API.
add-rule
Captures a team convention or best practice and adds it to the appropriate .claude/rules/ or .claude/agents/ file
deploying-vmcp-locally
Deploys a VirtualMCPServer configuration locally for manual testing and verification
toolhive-release
Creates ToolHive release PRs by analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow. Use when cutting a release, preparing a new version, checking what changed since last release, or when the user mentions "release", "version bump", or "cut a release".
checking-changes
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
code-review-checklist
Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability