القائمة
Validates operator chart contribution practices (helm template, ct lint, docs generation) before committing changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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".
Implements a GitHub user story from planning through PR creation, with research, codebase analysis, and structured commits.
Generates polished GitHub release notes for a ToolHive release by analyzing every merged PR, cross-referencing linked issues, dispatching expert agents to assess breaking changes, and producing a formatted release body. Use when the user provides a GitHub release URL, tag name, or says "release notes".
Finds flaky tests on the main branch by analyzing GitHub Actions failures, ranks them by frequency, and enters parallel plan mode to design deflake strategies. Use when you want to find and fix the flakiest tests.
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.
| name | check-contribution |
| description | Validates operator chart contribution practices (helm template, ct lint, docs generation) before committing changes. |
| allowed-tools | ["Bash","Read"] |
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.
cd "$(git rev-parse --show-toplevel)"/deploy/charts/operator && helm template test .
Verify the output contains valid Kubernetes YAML without errors.
ct lint
Report any linting errors or warnings.
helm-docs --dry-run
Verify that values.yaml variables are documented and the generated README.md matches.
✅ or ❌ Helm template renders successfully
✅ or ❌ Chart linting passes
✅ or ❌ Documentation up-to-date
Note: Chart version bumps are automated by the release bot. Feature PRs should NOT modify Chart.yaml.
Include specific errors for any failing checks with actionable remediation commands.