2_review

Generate a phase-aware review report of implementation changes against the current spec.

10|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/dixus/claudeframework --skill 2-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 2_review
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/2_review
Command: npx skills add https://github.com/dixus/claudeframework --skill 2-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the process of reviewing implementation changes and generating a formal report, reducing context-switching and ensuring traceability across phases.

Core Features & Use Cases

  • Phase-aware delta and full reviews with clear criteria coverage.
  • Generates a structured, actionable review document saved at .claude/reviews/<name>-review.md.
  • Supports both initial and subsequent delta cycles, with escalation to full review if needed.

Quick Start

Check the current project for a new implementation and run this skill to produce a phase-aligned review report.

Frequently Asked Questions about 2_review

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

FAQPage Schema
How do I generate a structured code review report for recent implementation changes?▼

Generate a structured code review report by identifying changes against the current spec and documenting findings to a dedicated review file. The skill operates in a phased, context-aware workflow that validates fixes and tracks gaps.

What is phase-aware code review and how does it manage implementation phases?▼

Phase-aware code review respects in-progress phases by focusing validation on the current phase's criteria. It identifies deltas against the current spec and generates a formal report, ensuring traceability across all implementation phases.

Can I run delta code reviews after fixing issues from a previous review cycle?▼

Yes, delta code reviews support subsequent cycles after fixes are applied. If the delta review reveals wider problems, it can escalate to a full review to ensure complete criteria coverage and spec validation.

Where does the code review report get saved and what format does it use?▼

The code review report is saved as a markdown file at .claude/reviews/<name>-review.md. This structured document provides actionable findings, phase-aligned criteria coverage, and traceable validation results for implementation changes.

How do I validate code fixes and track remaining gaps during a spec review?▼

Validate code fixes and track gaps by running a phase-aligned spec review that compares changes against current criteria. The workflow identifies unmet requirements, validates applied fixes, and documents all findings into a formal review file.

What is the best way to standardize code review reports across multiple development phases?▼

Standardize code review reports by using a phased, context-aware workflow that identifies spec deltas, validates fixes, and documents findings to a dedicated review file. This reduces context-switching and ensures consistent traceability across phases.