review

Validate implemented features against a specification file and fix blocker issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that implemented code accurately matches the requirements defined in a specification file, automatically fixing critical issues to maintain code quality and project integrity.

Core Features & Use Cases

  • Spec-based validation: Compares code changes against detailed requirements in a spec file.
  • Automated issue fixing: Automatically resolves 'blocker' and 'tech_debt' issues found during review.
  • Use Case: After a developer implements a new user authentication feature, they can use this Skill to verify that all acceptance criteria in the specs/feat-user-auth.md file are met and automatically fix any identified bugs before merging.

Quick Start

Use the review skill to validate the current branch against the spec file located at specs/feat-user-auth.md.

Frequently Asked Questions about review

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

FAQPage Schema
How do I validate code changes against a specification file before merging?

To validate code against a spec, compare your git diff with the criteria in the specification file to classify issues by severity and automatically fix blocker and tech_debt issues. This produces a structured JSON report verifying features match requirements.

Can I automatically fix code review issues found during spec validation?

Yes, spec validation can automatically fix code review issues by resolving all blocker and tech_debt severity issues in-place. It classifies issues by comparing the git diff against the spec and repairs actionable problems directly.

What is the best way to check if implemented features match project requirements?

The best way to check if implemented features match requirements is spec-based validation, which compares code changes against a detailed specification file and produces a structured JSON report classifying any discrepancies by severity.

How do I capture screenshots of critical UI paths during code validation?

During code validation you can optionally capture screenshots of critical UI paths while comparing the git diff against the spec. This visual evidence is included alongside the structured JSON report classifying issues by severity.

Does spec validation work with a git diff to verify work before merging?

Yes, spec validation works directly with a git diff to verify work before merging. It compares the diff against the specification file criteria, classifies issues by severity, and automatically fixes all blocker and tech_debt issues in-place.

What issue severity levels are automatically fixed during a spec-based code review?

During a spec-based code review, the severity levels automatically fixed are blocker and tech_debt. The validation process compares the git diff against the spec, resolves these actionable issues in-place, and generates a structured JSON report.