skills.rest
hacker-cb
hacker-cbCOMMUNITY
Explore all skills by this author →
GitHub

multi-review

Reviews a code change with Claude, security, and Codex sources and reports findings with per-source coverage.

Updated Jun 6, 2026
Search Tags:#diff analysis#code review#codex#multi-source#security review#pre-merge#findings report
One-click install
npx skills add https://github.com/hacker-cb/claude-code-plugins --skill multi-review-hacker-cb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-review
Source: https://github.com/hacker-cb/claude-code-plugins/tree/main/plugins/hcb-dev/skills/multi-review
Command: npx skills add https://github.com/hacker-cb/claude-code-plugins --skill multi-review-hacker-cb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Before merging or shipping a change, developers need an independent, multi-angle review that reports findings without silently applying fixes, and that honestly states what each review source actually covered. ## Core Features & Use Cases - Multi-source review round: Runs one review over the current change using Claude's finders, the security angles, and a Codex pass, then consolidates everything into a single report. - Coverage accounting: Produces a row per source stating what it covered, including explicit n/a or partial rows when a source was skipped or could not run. - Scoped reviews: Supports narrowed reviews (a path or focus like "only error handling") and working-tree-only reviews based on HEAD, while refusing to treat an audit of untouched code as a change review. - Use Case: Before merging a feature branch, ask for a review of the diff; the skill resolves the correct base, runs all sources at the appropriate rung, and returns a findings table you act on yourself. ## Quick Start Ask the assistant to review the current change with multi-review before merging the branch.

Frequently Asked Questions about multi-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a code change with multiple reviewers before merging?▼

Invoke the multi-review skill on the current change; it opens one review round with Claude, security, and Codex sources and returns a single report of findings plus a coverage row per source. It never applies fixes, so you decide what to do with the results.

Can I review only part of a diff or just uncommitted changes?▼

Yes. You can narrow the round to a path or a focus such as error handling, or request a working-tree-only review whose base is HEAD. The narrowing applies to every source alike.

What happens if the Codex CLI is not installed during a review?▼

A source that cannot run, such as a missing Codex CLI or exhausted model limits, records its own loss in the round. Its row in the report states that it did not report, so coverage gaps are never hidden.

Does multi-review fix the issues it finds automatically?▼

No. The skill is strictly report-only: it hands findings and coverage to the caller and never applies fixes or patches. The caller decides which findings to act on.

When should I not use multi-review on a codebase?▼

Do not use it to audit existing code that no change touched, since a round reviews a diff and reports nothing when the diff is empty. It is also not an auto-trigger on every edit.

Related Skills

Explore More Software Engineering Skills→
gioegioe

review-commits

Coordinate parallel AI code reviews against a task's git diff.

Community
Advanced
heliohqheliohq
88

handoff

Coordinates GitHub pull requests from commit to ready-for-merge state.

Official
Advanced
satsilemsatsilem
4

aristotle

Classify items into a mutually exclusive taxonomy with 3-7 defined categories.

Community
Advanced
crowicrowi
1.1k

crowi-review

Runs adversarial code reviews on git diffs using Codex with structured findings and selective fixes.

Official
Advanced