deep-review

Runs a blind multi-lens panel review of a git diff and returns one verdict.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill deep-review-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/joydai2026-del/skills/tree/main/deep-review
Command: npx skills add https://github.com/joydai2026-del/skills --skill deep-review-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-reviewer code reviews miss defects because the agent that wrote the code shares the same blind spots as the one reviewing it. This Skill fires several independent reviewers that are blind to each other, plus a different model family (Codex), then reconciles their findings into one verdict before you merge. ## Core Features & Use Cases - Blind parallel panel: Launches adversarial, reality-check, test-coverage, security, and spec-alignment lenses in parallel, each reviewing the identical diff without seeing other reviewers' findings. - Cross-model jury vote: Runs the Codex CLI as a different-model-family reviewer, with a labeled same-family fallback when Codex is unavailable, and weights convergent findings most heavily. - Risk-tiered depth and triage: Scales review depth by change sensitivity (auth, secrets, billing, migrations, public APIs, infra), dedupes findings, and sorts them into fix-now, nit, and owner-decides buckets with a SHIP / FIX-FIRST / RETHINK verdict. - Use Case: Before merging a branch that touches authentication, run the panel to get a security-mandatory review, a list of must-fix findings with file:line references, and a verdict that still requires your explicit sign-off. ## Quick Start Ask the agent to run a deep review of the current branch against its base before merging, optionally with --fix to apply clear localized fixes or --pr <number> to review a GitHub pull request.

Frequently Asked Questions about deep-review

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

FAQPage Schema
How do I run a multi-agent code review before merging a branch?▼

Invoke the deep review command on your local branch and it detects the merge base, captures the committed diff, and launches parallel independent reviewer lenses. It returns a single SHIP, FIX-FIRST, or RETHINK verdict with must-fix findings listed by file and line.

How do I review a GitHub pull request with multiple AI reviewers?▼

Pass --pr with the pull request number so every lens reviews the identical PR diff fetched via gh. Findings can optionally be posted as inline PR comments with --comment, gated on repo ownership and your confirmation.

Does the review modify my code automatically?▼

No, the default mode is report-only and never edits your tree. Fixes are applied only with --fix, never on the default branch, and the panel re-runs once on the patched diff with a cap of three rounds per invocation.

What happens when the Codex cross-model review is unavailable?▼

If Codex returns an error, usage limit, or empty output, it is treated as unavailable rather than a clean vote. A second fresh adversarial reviewer runs as a labeled same-family fallback, and its agreement never counts as convergent cross-model confirmation.

When should I not use a multi-lens panel review?▼

Skip it for quick single-read checks, simple diff bug-hunts, or reviewing an external repository before installation, which needs a separate repo-safety scan. A clean review also does not replace live end-to-end verification of user-facing surfaces.