exhaustive-code-review

Reviews every diff unit across six parallel subagent lanes with a frozen coverage ledger.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill exhaustive-code-review-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exhaustive-code-review
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/dev-core/skills/exhaustive-code-review
Command: npx skills add https://github.com/josippapez/ai-setup --skill exhaustive-code-review-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard code reviews stop when the reviewer stops finding issues, which means a later re-run often surfaces problems that were present all along. This Skill replaces that subjective stopping point with a verifiable finish line: every unit of the changed surface must carry an explicit verdict from every review lane before the review is considered done. ## Core Features & Use Cases - Frozen review surface: Enumerates changed hunks, whole touched files, and every caller of changed symbols into a ledger stored at .git/exhaustive-review/<branch>.md before any reviewing begins. - Six parallel review lanes: Dispatches one subagent per lane (correctness, concurrency, security, contracts/blast radius, tests, reuse/consistency), each covering the entire unit list with per-unit verdicts. - Gap closure and re-review: Re-dispatches lanes with empty cells, deduplicates findings by file:line, and rebuilds the surface after fixes so re-reviews cover moved code. - Use Case: Before merging a large branch touching authentication and database migrations, run this Skill to confirm every hunk, file, and caller was checked by all six lanes, with pre-existing issues reported separately from introduced ones. ## Quick Start Ask the AI to run an exhaustive code review of the current branch against its merge base and confirm the six-lane fan-out when prompted.

Frequently Asked Questions about exhaustive-code-review

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

FAQPage Schema
How do I run an exhaustive code review on a branch before merging?

Ask for an exhaustive or full review of the branch against its merge base. The Skill first shows the diff size and asks you to confirm, then freezes the surface into a ledger and dispatches six lane subagents that each return a verdict for every unit.

What is the difference between exhaustive-code-review and the built-in /code-review?

The built-in /code-review is a single fast pass suited for quick looks. exhaustive-code-review fans out six subagents over an enumerated unit list and is not finished until every unit has a verdict from every lane, so a re-run should find nothing new.

When should I not use an exhaustive multi-agent code review?

Skip it for small diffs of roughly three units or fewer, where running the lanes sequentially yourself is cheaper. It also wastes budget on low-risk changes that one careful pass would cover, since each pass spends six subagents reading the whole surface.

Can I run only some review lanes to reduce cost?

Yes, lanes can be dropped when the diff cannot violate them, such as running only the consistency lane for docs-only changes. Diffs touching auth, money, user data, or migrations always require all six lanes, and dropped lanes must be named in the report.

How does re-review work after review findings are fixed?

The unit list is rebuilt against the new diff because fixes move code. A unit keeps its earlier verdict only if its content is byte-identical; everything else goes back through the lanes, and new findings on unchanged units are flagged as coverage gaps.