deep-review

Orchestrates multi-agent code review of PRs, diffs, and branches across independent review dimensions.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/SmallAi-API/smaihub --skill deep-review-smallai-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/SmallAi-API/smaihub/tree/main/.agents/skills/deep-review
Command: npx skills add https://github.com/SmallAi-API/smaihub --skill deep-review-smallai-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, vitest, and includes scripts (resource) and references (resource) components.

What problem does it solve? Code reviews done by the same agent that wrote the code tend to rubber-stamp it, and single-pass reviews miss cross-cutting issues. This Skill runs independent, dimension-focused reviewers with adversarial verification so findings are confirmed before they reach the report. ## Core Features & Use Cases - Two review modes: Light mode dispatches one independent reviewer against quick checklists for ordinary PR reviews; Deep mode runs a full multi-agent pipeline (dimension reviewers, verification, duplicate consolidation, structured report) only on explicit request. - Fourteen review dimensions: logic, security, performance, release risk, compatibility, UX, observability, reuse-architecture, and more, each with executable rules and pruning criteria. - Anti-hallucination verification: candidate findings are independently falsified and labeled confirmed, false positive, or need-more-context, with severity, likelihood, and release-blocking status. - Use Case: After finishing a feature branch, ask for a deep review to get a structured report with a merge verdict, P0/P1/P2 findings, pre-deploy checklist, and legacy issues handed off to their owners. ## Quick Start Ask the agent to run a deep review on the current branch or a specific PR, for example: run deep review on PR #123.

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 on a pull request?

Explicitly request a deep review, such as "run deep review on PR #123". The skill spawns independent dimension reviewers, verifies each finding adversarially, consolidates duplicates, and renders a structured report with a merge verdict.

What is the difference between light review and deep review mode?

Light mode is the default for ordinary review requests and uses one independent reviewer against quick checklists with at most one verification round. Deep mode runs only on explicit request and orchestrates parallel dimension reviewers, verification, consolidation, and a full report.

Which code review dimensions does deep-review cover?

It covers fourteen dimensions including logic, security, performance, release risk, compatibility, UX, observability, code style, reuse-architecture, business-logic design, new-feature design, workflow, and skill freshness. Dimensions that cannot apply to a diff are pruned before reviewers run.

Does deep-review work outside Claude Code and Codex?

Deep mode currently supports only Claude Code and Codex, each with its own orchestration manual. In other environments the skill tells the user deep mode is unsupported and offers light mode instead.

How does the review avoid false positives and self-approval?

Reviewers are independent agents that never share context with the code author, and every candidate finding goes through a separate verification pass returning confirmed, false_positive, or need_more_context. Findings are also calibrated against the codebase's existing standards.

When should I not use deep review mode?

Do not use it for casual review asks, follow-up re-reviews after fixes, or explanation questions about a change; those use light mode. Deep mode runs at most once per logical requirement unless the user explicitly requests another pass.