code-review

Plugin code-review from marketplace juanmhidalgo-plugins in juanmhidalgo/claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (6)

• branch-review

  Use when reviewing branch changes or PRs for merge readiness with severity classification. Do NOT use for general code quality advice — use dedicated linters. - code-review - branch-comparison - diff-analysis - pr-preparation - security-checklist - "review branch changes" - "compare branches" - "ana

• coverage-gate

  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. - coverage - coverage-gate - threshold - ci-coverage - orgoro-coverage

• posting-a-pr-review

  Use when the user explicitly asks to post review findings to a GitHub PR — as a Request changes review with inline comments on the changed lines. Do NOT use to run a review (/code-review:pr, :branch, :staged), to reply to or resolve comments already on the PR (/code-review:dismiss), or to triage ano

• receiving-code-review

  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). - code-review-feedback - review-reception - feedback-verification - pushback-patterns - "received code review" - "p

• review-fixes-plan

  Use when generating or managing a REVIEW_FIXES.md tracking document after a code review session. Do NOT use for tracking issues outside of code review workflows. - fix-tracking - issue-management - review-fixes - progress-tracking - "create fix tracking document" - "track code review fixes" - "docum

• technical-decisions

  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. - technical-decisions - implementation-choices - architecture-decisions - trade-offs - "decide between approaches" - "multipl

Slash commands (14)

• /code-review:branch

  Use to review branch changes for merge readiness in a reviewer that has NOT seen this conversation — the reviewer forms its own read of the code, so it is the right choice when this session wrote or planned the code under review. Do NOT use for staged-only review (use /code-review:staged) or PR feed

• /code-review:coverage-gate

  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). - coverage - coverage-gate - threshold - pre-push - ci-coverage - "check coverage" - "coverage gate" - "will cover

• /code-review:dismiss

  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. - false-positive - dismiss-comment - resolve-thread - pr-feedback - "dismiss false positives" - "resolve PR comments" - "dismiss

• /code-review:fixes-plan

  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. - fixes-tracking - review-fixes - issue-tracking - bug-tracking - "create fixes plan" - "track review fixes" - "generate f

• /code-review:implement-fix

  Use when REVIEW_FIXES.md exists and you want to implement tracked issues. Do NOT use without a REVIEW_FIXES.md — run /code-review:fixes-plan first. - implement-fix - code-fix - bug-fix - review-fixes - "implement review fixes" - "fix review issues" - "apply code fixes" - "implement bug fixes" - tech

• /code-review:mark-fixed

  Use to verify and mark issues as fixed in REVIEW_FIXES.md. Do NOT use without an existing REVIEW_FIXES.md — run /code-review:fixes-plan first. - verify-fix - mark-fixed - fix-verification - issue-completion - "mark as fixed" - "verify fixes" - "check if fixed" - "mark issue completed

• /code-review:pipeline

  Use only when the user explicitly asks for the autonomous PR pipeline (by name, or "run the pipeline on PR N"), or when /ship hands off a PR that Copilot commented on. It edits, commits and pushes without asking. Do NOT use to look at or triage PR comments (use /code-review:triage), for draft PRs, o

• /code-review:pr

  Use when you need a thorough code review of a pull request, reported in this session. Do NOT use for staged or branch-only reviews (use /code-review:staged or :branch), and do NOT use to post a review to GitHub — this command never writes to the PR. - pull-request - code-review - github-pr - multi-a

• /code-review:receive

  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. - code-review - receive-feedback - review-report - cross-session - "received code review feedback" - "here's the review from the other session" - "process this c

• /code-review:resolve-fixed

  Use after marking issues as fixed in REVIEW_FIXES.md to close corresponding GitHub threads. Do NOT use before verifying fixes — use /code-review:mark-fixed first. - resolve-threads - github-comments - pr-threads - close-threads - "resolve GitHub threads" - "close PR threads" - "resolve fixed issues"

• /code-review:staged-pipeline

  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). - staged-pipeline - review-and-fix - pre-commit - staged-changes - autonomous-review - "review and fix stage

• /code-review:staged

  Use to review staged changes before committing, in a reviewer that has NOT seen this conversation — the right choice when this session wrote the code being staged. Do NOT use for branch-wide review (use /code-review:branch), full PR review (use /code-review:pr), or to also fix what it finds (use /co

• /code-review:tech-debt

  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. - tech-debt - technical-debt - code-quality - maintainability - refactoring - "check for tech debt" - "analyze technical debt" - "review code qual

• /code-review:triage

  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. - ai-feedback - copilot-review - gemini-review - false-positives - pr-comments - "triage AI feedback" - "review bot comment

Subagents (14)

• branch-reviewer

  Code review specialist for branch comparisons and PR preparation. Use PROACTIVELY when: (1) Reviewing branch changes before merge, (2) Comparing current branch vs main/develop, (3) Preparing code for PR submission, (4) Analyzing diffs for security/performance issues.

• bug-scanner

  Shallow scan for obvious bugs in PR changes. Agent #2 in parallel review.

• claudemd-compliance-reviewer

  Review PR changes for CLAUDE.md compliance. Agent #1 in parallel review.

• code-comments-reviewer

  Check if PR changes comply with guidance in code comments. Agent #5 in parallel review.

• comment-fetcher

  Runs `gh feedback fetch --split` for a PR and returns the printed metadata as structured output. First stage of the triage-comments workflow; never reads a comment body.

• comment-verifier

  Verifies a single PR review comment against actual code. Returns VALID BUG, FALSE POSITIVE or NEEDS INVESTIGATION with evidence. Spawned by the pipeline to triage comments in parallel.

• finding-verifier

  Verifies a single review finding against the actual code. Returns CONFIRMED, PLAUSIBLE, or REFUTED with evidence. Spawned in parallel to triage findings produced by the review agents.

• fix-implementer

  Implements a single code fix from review feedback. Spawned by the review workflow's fix mode (pipeline, staged-pipeline, feature-dev and github-issues review loops), one per finding, in order. Use when delegating individual fix tasks.

• git-history-reviewer

  Review git blame and history for context on modified code. Agent #3 in parallel review.

• pr-comments-reviewer

  Check previous PR comments that may apply to current changes. Agent #4 in parallel review.

• pr-feedback-analyst

  Analyze and triage PR feedback from AI reviewers (Copilot, Gemini). Use when: (1) PR has bot comments to review, (2) Need to separate valid issues from false positives, (3) Prioritizing code review feedback.

• silent-failure-reviewer

  Hunts silent failures in PR changes: swallowed errors, fallbacks that hide a failure, errors logged without context or not at all. Agent #6 in parallel review.

• spec-conformance-reviewer

  Reviews a diff against the spec it was built from (a closed issue, a SPEC/PLAN file): requirements missing, partial or implemented wrong, and behaviour nobody asked for. Spawned by the review commands as the Spec axis, separate from the defect review.

• tech-debt-reviewer

  Technical debt analyzer for pre-merge reviews. Use PROACTIVELY when: (1) Checking if changes introduce maintainability issues, (2) Evaluating code quality before merge, (3) Identifying refactoring opportunities in new code.

Similar plugins