review

Plugin review from marketplace melodic-software in melodic-software/claude-code-plugins. Commands read from the repo's manifest — today.

Skills (8)

• code-review

  CI code-review lane for a GitHub pull request. High-signal correctness and maintainability findings only, scoped out of security when a security lane exists. When the bundled code-review skill resolves in this session, prefer it for a session-driven review of the current diff or a named PR; this ski

• council

  Council review: a panel of configured reviewer members (provider, model, brief, effort), chosen for this change by its paths, size or merge risk, reviews one change and writes one ranked findings report; optional repeated rounds run /review:fanout fix between them and stop on a checkable condition.

• explain-change

  Pull request explainer: a markdown digest of one PR (why, before and after, a checked risk map, annotated hunks, an optional quiz) with an optional interactive view. Never posts to the PR or gates merge. Use when asked to 'explain this PR' or 'walk me through this pull request', for a 'digest' of a

• fanout

  Breadth review: fans a change out to many reviewers at once (this plugin's reviewer agents, the project's per-concern criteria docs, orchestrator review plugins) and merges their findings into one deduplicated, severity-ranked report on disk. Use when asked for a breadth review of a change (every re

• merge-risk

  Merge-risk rating of one pull request: alignment with its closing issue, impact, verification, reversibility and error detection, each LOW to CRITICAL and checked blind, plus a demote flag that can only send an unattended merge to a human. Never posts or gates. Use when asked 'how risky is this PR',

• quality-gate

  Single-lens review checkpoint between 'code works' and 'code is ready': self, code, code-design, architecture, security, spec, close-out, downstream, pr, criteria, slice or restatement mode, each delegated to its reviewer. Use when asked to 'review this', for a 'self-review' or 'quality gate', a cod

• security-review

  CI security-review lane for a GitHub pull request. Logic, trust-boundary, and Actions security findings static analysis misses. When the plugin-backed built-in security-review command resolves in this session, prefer it for a one-off security pass over the current branch; this skill for the CI lane

• setup

  Check or apply the review plugin's repository setup: the standards index and docs/conventions/review.yaml settings.

Subagents (9)

• architecture-guardian

  Architecture enforcement specialist. Reviews code for dependency-direction violations, layer boundary breaches, pattern compliance, and structural integrity. Use when adding new projects or modules, modifying project references, creating cross-module interactions, or before PRs touching architecture

• brief-reviewer

  Read-only reviewer that runs exactly the review brief it is dispatched with: a per-concern criteria slice, a downstream blast-radius search, a spec comparison, a restatement batch, or a pull request risk-map check. Dispatched by /review:quality-gate (slice, code-design, downstream, spec, close-out a

• ci-log-auditor

  CI run auditor, read-only over the reviewed code by instruction. Detects masked failures, silently-skipped jobs, suspicious 'success' steps, performance outliers, retry loops, and stderr drift, issues NOT raised as ##[error] markers. Use for 'audit run X', 'thorough CI review', 'why did this pass wh

• code-reviewer

  Code review specialist for any ecosystem. Reviews a finished change set for quality, convention adherence, and design judgment that automated tooling misses. Use when the user says 'review' or 'check the code', or before creating a PR. Not after every edit or for a typo-sized tweak, not for issues l

• doc-drift-detector

  Documentation freshness and accuracy specialist. Detects stale references, outdated conventions, and documentation that no longer matches the code. Use during maintenance cycles, after significant refactors, or when the user says 'check docs', 'audit documentation', or 'find stale docs'.

• ecosystem-specialist

  Multi-language build, test, and lint specialist. Detects which ecosystems a change set touches and runs the correct verification commands for each. Use when the user says 'build', 'test', 'lint', or 'check'. Not after every edit.

• lane-verifier

  Read-only hunter or verifier for the CI review lanes and for model diversity in the /review:fanout-sweep workflow: hunts candidate findings in one slice of a pull request or one change set, or tries to refute one candidate another agent produced, as its brief names. Dispatched by /review:code-review

• security-reviewer

  Cross-ecosystem security audit specialist. Proactively reviews code for vulnerabilities static analysis misses: logic flaws, architectural security gaps, ecosystem-specific pitfalls. Use when modifying authentication, authorization, data handling, API endpoints, or any code processing user input, an

• stage-normalizer

  Runs one judgment stage of the review plugin's findings-normalization pipeline as its brief names it: Stage 0 extraction of reviewer output into records, or Stage 3 dedup. Holds Read only. Dispatched by /review:fanout, /review:council and the /review:fanout-sweep workflow; not intended for direct ad

Hooks (1)

• PreToolUse

  node

Similar plugins