Command
Use to prevent CI coverage failures before pushing by checking coverage against CI-configured thresholds. Do NOT use as a replacement for running tests (use your test command directly).
Command
Use to prevent CI coverage failures before pushing by checking coverage against CI-configured thresholds. Do NOT use as a replacement for running tests (use your test command directly).
Command
Use when PR comments are false positives that should be closed with justification. Do NOT use for valid findings that need fixes — use /code-review:implement-fix instead.
Command
Use when a code review session has produced findings that need tracking before implementation. Do NOT use without prior review output — run /code-review:staged or :branch first.
Command
Use when REVIEWFIXES.md exists and you want to implement tracked issues. Do NOT use without a REVIEWFIXES.md — run /code-review:fixes-plan first.
Command
Use to verify and mark issues as fixed in REVIEWFIXES.md. Do NOT use without an existing REVIEWFIXES.md — run /code-review:fixes-plan first.
Command
Use when you want to resolve all PR feedback autonomously in a single pass. Do NOT use for draft PRs or when you need manual control over individual fixes.
Command
Use when you need a thorough code review of a pull request. Do NOT use for staged or branch-only reviews (use /code-review:staged or :branch).
Command
Use when pasting review output from /code-review:staged or :branch. Do NOT use for PR triage (/code-review:triage) or to run a new review.
Command
Use after marking issues as fixed in REVIEWFIXES.md to close corresponding GitHub threads. Do NOT use before verifying fixes — use /code-review:mark-fixed first.
Command
Use when you want to review and fix staged changes in a single session before committing. Do NOT use for PR reviews (use /code-review:pipeline) or read-only reviews (use /code-review:staged).
Command
Use to review staged changes before committing. Do NOT use for branch-wide review (use /code-review:branch) or full PR review (use /code-review:pr).
Command
Use to analyze staged changes or branch diff for technical debt and maintainability issues before merge. Do NOT use for bug detection or security review.
Command
Use to triage PR feedback from AI reviewers and verify validity before implementing. Do NOT use without an open PR with bot comments — use /code-review:branch for local review.
Skill Claude CodeCodex
Use when reviewing branch changes or PRs for merge readiness with severity classification. Do NOT use for general code quality advice — use dedicated linters.
Skill Claude CodeCodex
Use when checking code coverage against CI-configured thresholds before pushing or during pipeline execution. Do NOT use for general test writing or coverage tool configuration.
Skill Claude CodeCodex
Use when receiving code review feedback to verify suggestions before accepting or pushing back. Do NOT use to run a review (/code-review:staged) or for PR triage (/code-review:triage).
Skill Claude CodeCodex
Use when generating or managing a REVIEWFIXES.md tracking document after a code review session. Do NOT use for tracking issues outside of code review workflows.
Skill Claude CodeCodex
Use when multiple implementation approaches exist during code review and a decision must be made. Do NOT use for general architecture planning outside of code review context.
Plugin Claude Code
Systematic debugging and incident response: structured triage, root cause analysis, regression guards, error pattern recognition, and blameless postmortem generation.
Command
Use when facing any error or unexpected behavior that requires diagnosis before fixing. Do NOT use for quick classification only — use /debug:triage for that.
Command
Use to manage an incident through its lifecycle: triage on detection, status updates during, blameless postmortem after. Do NOT use for ordinary debugging — use /debug:debug for single-engineer bug-hunting.
Skill Claude CodeCodex
Use when tests fail, builds break, or behavior doesn't match expectations. Covers triage methodology and regression guards. Do NOT use for writing new features or general code quality.
Skill Claude CodeCodex
Use to run an incident response workflow — initial triage, status updates during, blameless postmortem after. Do NOT use for ordinary debugging — use debugging-strategies for single-engineer bug-hunting.
Plugin Claude Code
Critical feature discussion, idea refinement, and adversarial review of technical documents.