deep-review

Review git diffs against coding standards and completeness criteria.

Updated May 17, 2026
One-click install
npx skills add https://github.com/ievo-ai/skills --skill deep-review-ievo-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/ievo-ai/skills/tree/main/plugins/ievo/skills/deep-review
Command: npx skills add https://github.com/ievo-ai/skills --skill deep-review-ievo-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a thorough code review of the diff before committing, catching issues missed by automated tools but discovered in human PR review.

Core Features & Use Cases

  • Structured Review: Conducts a 11-point code review, covering completeness, consistency, and correctness.
  • Independent Subagent: Spawns a deep-reviewer subagent for unbiased and context-independent analysis.
  • Scope Options: Supports reviewing staged changes, working tree, or a specified git range.
  • Use Case: Before committing a significant change, especially after a refactor, or to get a second opinion on a diff.

Quick Start

Run the command /ievo:deep-review in your project directory to initiate a deep code review.

Frequently Asked Questions about deep-review

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

FAQPage Schema
How do I review code diffs for commit safety before pushing changes?

Review code diffs for commit safety by running a comprehensive 11-point code review that analyzes staged changes or working tree diffs to ensure compliance with predefined coding standards and completeness criteria before execution.

What is a deep code review and how does it find issues missed by automated tools?

A deep code review is a structured 11-point analysis of a git diff that catches completeness, consistency, and correctness issues typically missed by automated tools but found in human PR review.

Do I need git CLI to analyze working tree changes for a pre-commit review?

Yes, you need git CLI installed to generate diffs for the pre-commit review, which supports analyzing staged changes, the working tree, or a specified git range for error path analysis.

Can I analyze error paths and code quality on a specific git commit range?

Yes, you can analyze error paths and code quality on a specific git commit range by providing the range to the review process, which then evaluates the diff against coding standards using Sonnet-level reasoning.

What's the best way to get an unbiased code review of a refactor before committing?

Get an unbiased code review of a refactor by spawning an independent deep-reviewer subagent, which provides context-independent analysis of the diff to verify correctness and completeness before you commit.

When should I use a structured code review instead of standard linters?

Use a structured code review instead of standard linters after a significant change or refactor, when you need Sonnet-level reasoning to evaluate compliance with predefined coding standards and uncover issues missed by automated tools.