メニュー
Lifecycle of implementing a backlog issue - triage, scope decisions, the PR flow and the closing retrospective comment. Use when asked to implement an issue from the tracker.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/shopsys/helm --skill implement-issueコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Fan-out code review of multiple/all open PRs - one parallel worktree-isolated agent per PR, each following the review-pr skill protocol, then cross-PR verification, cleanup and summary. Use when asked to review all open PRs or several PRs at once; a single PR needs only review-pr.
Detailed code review of ONE pull request - scope vs its (possibly stacked) base, verification-first findings (render + tests + web research), posting a GitHub review with anchored inline comments signed "Claude Agent (CR)". Use when asked to review a specific PR; for all open PRs at once use review-open-prs, which fans this out.
Conventions for creating GitHub issues in this repository - body structure, title prefixes, the label taxonomy and cross-linking rules. Use whenever filing new issues or turning analysis/review findings into backlog items.
SKILL.md を表示中
| name | implement-issue |
| description | Lifecycle of implementing a backlog issue - triage, scope decisions, the PR flow and the closing retrospective comment. Use when asked to implement an issue from the tracker. |
Related: links: is another issue a prerequisite, or would it supersede this work
(e.g. #19 CronJobs vs #3 supercronic)? Raise conflicts before implementing.behavior-change label ⇒ plan the golden regen + deviations entry from the start.Follow helm-kubernetes-guidelines (conventions/gotchas) and prepare-pr
(checklist, verification suite, commit/PR conventions). PR body starts with Closes #N —
one PR may close several issues when they share code (Closes #31 + Closes #14).
Whenever the implementation differs from the issue's proposal:
Follow watch-pr — CI, Copilot triage, threads stay open.
When the final shape differs from the original proposal, post a closing summary comment on the issue: Implemented (what actually shipped, with the PR link) and Not implemented (deliberately) (each dropped item + reason). This keeps the tracker truthful after the issue auto-closes — see shopsys/helm#12 for the reference example.