Menu
SkillsMP has collected 9 skills from shopsys/helm. Open a skill to review its source and details.
Showing 9 of 9 collected skills.
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…
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…
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.
Diagnosing a failed deploy on a real cluster - identifying which phase failed from the end states, where the logs are, recovery commands, and what must NOT be done. Use when a helmfile/wrapper deploy fails or behaves unexpectedly.
Helm and Kubernetes best practices plus this repository's hard-won gotchas (template pitfalls, hook lifecycle, secrets patterns, determinism rules). Read BEFORE writing or modifying any chart template, values file or hook.
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.
End-to-end workflow for preparing a pull request in this repository - branching, implementation checklist, the full verification suite, commit/PR conventions and stacked-PR handling. Use whenever implementing an issue or any change that will become a PR.
Porting changes from the legacy shopsys/deployment package (upstream PRs, manifest fixes) into these charts. Use when asked to review/port upstream deployment PRs or to check what changed upstream.
Watch a pull request after creation - CI checks, Copilot review comments including suppressed ones, and the protocol for discussing findings with Copilot. Use right after opening a PR, or when asked to check/handle review feedback on one.