review

Validate software changes against acceptance criteria and design artifacts.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Zxela/claude-create --skill review-zxela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Zxela/claude-create/tree/main/skills/review
Command: npx skills add https://github.com/Zxela/claude-create --skill review-zxela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the validation of a software change against its acceptance criteria and design artifacts, ensuring alignment before approval.

Core Features & Use Cases

  • Input validation: Verifies that the task includes an id, title, acceptance criteria, and an implementation reference; checks required paths like technical_design and adr exist.
    • Consistency checks: Ensures every acceptance criterion has an associated test and that tests actually validate the criterion.
  • Audit-ready decisions: Produces a structured APPROVED or REJECTED decision with file/line references and rationale for each criterion.

Quick Start

Call the Review Skill with a task object describing the feature change, supply the implementation commit and changed files, and reference the TECHNICAL_DESIGN.md and ADR.md. The agent will return a clear verdict and actionable feedback.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review against acceptance criteria?

Code review for acceptance criteria compliance validates software change-sets by checking every criterion has associated tests aligned with TECHNICAL_DESIGN.md and ADR.md. It enforces input validation for task ids and implementation references, outputting a structured APPROVED or REJECTED verdict with rationale.

Can I verify code changes against technical design documents automatically?

Verifying code changes against technical design documents requires supplying the implementation commit, changed files, and referencing TECHNICAL_DESIGN.md and ADR.md. The system aligns change-sets with these artifacts to ensure design compliance, producing audit-ready APPROVED or REJECTED decisions with rationale.

Do I need tests for every acceptance criterion to pass code review?

Every acceptance criterion requires an associated test to pass code review. The consistency check validates that tests actually validate the criterion, and missing tests trigger a REJECTED verdict with specific feedback indicating which criteria lack proper test coverage.

What is the best way to ensure code compliance before approval?

Ensuring code compliance before approval requires validating change-sets against acceptance criteria, technical design, and ADR references. This approach enforces criteria have tests, aligns with design artifacts, and generates audit-ready APPROVED or REJECTED decisions with file and line references.

Does automated code review work with ADR and technical design files?

Automated code review works with ADR and technical design files by verifying required paths like technical_design and adr exist. It aligns implementations with architecture decision records and design documents to determine compliance and quality before generating a verdict.