review-code-deeply

Reviews code diffs with parallel sub-agents across multiple perspectives and severity tiers.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill review-code-deeply-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code-deeply
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/review-code-deeply
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill review-code-deeply-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing large code changes single-handedly leads to shallow, inconsistent feedback. This Skill orchestrates multiple parallel review sub-agents to examine your own diffs from many angles, then merges and deduplicates findings into a prioritized must / imo / nits report. ## Core Features & Use Cases - Parallel bundle reviewers: Splits the diff into directory-based bundles of 5-8 files and assigns each to a dedicated sub-agent, plus a mandatory cross-file flow-integrity reviewer that catches wiring gaps, contract mismatches, and broken error propagation. - Severity triage and merging: Collects all agent findings, drops ungrounded claims, deduplicates overlapping reports, and finalizes severity using shared severity.md and output.md references from the single-pass /review-code skill. - Large-diff escalation: For diffs over 20 files or 1000 changed lines, optionally runs an additional independent reviewer focused on destructive failure scenarios. - Use Case: After finishing a feature branch touching 30 files, ask for a deep review and receive a consolidated report listing each issue with its location, perspective, and confirmed severity. ## Quick Start Ask the assistant to deeply review the current branch diff against origin/HEAD with a focus on correctness and error handling.

Frequently Asked Questions about review-code-deeply

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

FAQPage Schema
How do I run a deep multi-perspective code review on my diff?

Invoke the skill with an optional diff range and focus areas; it defaults to origin/HEAD...HEAD. It splits changed files into bundles, launches parallel review sub-agents, and returns a merged report with must, imo, and nits severity levels.

What is the difference between review-code and review-code-deeply?

review-code is a single-pass reviewer holding the severity criteria and output format. review-code-deeply reuses those references but parallelizes the work across multiple sub-agents for higher coverage on larger diffs.

When should I not use parallel deep code review?

Avoid it for diffs of three files or fewer, where orchestration cost exceeds the benefit; delegate to the single-pass version instead. Also skip it when a quick, lightweight review was requested.

Does the deep review modify or fix my code automatically?

No. The skill only reports findings with severity levels and never edits code, commits changes, or posts anything to GitHub. All fixes remain manual decisions by the author.

How are duplicate findings from multiple reviewers handled?

During the merge phase, duplicate findings on the same location are consolidated into one entry, cross-reviewer agreements are noted as higher confidence, and findings without traceable evidence in the diff are discarded.