deep-review

Runs five parallel perspective-based subagent code reviews on a git worktree and merges findings into one verdict.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-pass code reviews miss issues outside the diff, edge cases, and untested paths. This Skill reviews the same diff through five distinct lenses in parallel, then has the parent agent verify and deduplicate every finding before anything reaches a PR or report. ## Core Features & Use Cases - Five fixed review perspectives: implementation/codebase consistency, intent and design, correctness and tests, runtime quality, and security, each run as an isolated subagent on a full git worktree. - Parent-agent adjudication: the orchestrating session reads each intermediate review file, merges duplicates, rejects false positives, and re-grades severity before producing output. - Three output modes: inline PR review comments via the GitHub API, a markdown report file, or direct fixes to the working tree for non-design changes. - Use Case: Before merging a large pull request, ask for a deep review to get verified findings with file:line evidence posted as inline PR comments, plus a summary of rejected false positives. ## Quick Start Ask the agent to deep-review the current uncommitted changes or a specific PR number, for example by saying "deep-review PR #123 and post the findings as review comments".

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-perspective code review on a pull request?▼

Pass the PR number or URL and the skill fetches the diff with gh, creates a detached git worktree, and launches five parallel review subagents covering implementation, design, correctness, runtime, and security. Findings are verified by the parent agent and posted as one PR review with inline comments.

What is the difference between deep-review and fusion-review?▼

deep-review uses a single model with five different review perspectives, while fusion-review compares multiple models on the same perspective. They are complementary and can be used together depending on whether you need viewpoint diversity or model diversity.

Can the review subagents modify my repository or post to the PR?▼

No. Subagents run read-only on a disposable git worktree and may only write one intermediate review file each. All repository fixes, PR comments, and final reports are produced by the parent agent after reading and verifying those files.

Why does the review use a git worktree instead of just the diff?▼

Checks like DRY violations, convention consistency, and caller impact cannot be judged from diff text alone. The worktree gives each reviewer the full codebase so it can grep for call sites and compare against existing patterns.

When should I not use deep-review?▼

Avoid it for quick checks, since launching five subagents is costly. For lightweight review of uncommitted changes use a local-reviewer agent, and for triaging many waiting PRs use a dedicated PR-processing skill instead.