review

Consolidate architectural, domain, and test feedback into an auditable review report.

Updated May 13, 2026
One-click install
npx skills add https://github.com/usetheodev/theo-ui --skill review-usetheodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/review
Command: npx skills add https://github.com/usetheodev/theo-ui --skill review-usetheodev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill enforces the most rigorous gate for the ecosystem by generating domain-aware reviewers and consolidating their findings into a single, auditable report.

Core Features & Use Cases

  • Spawns specialized review agents (architecture, tests, wiring, cross-validation, domain) after /implement validation.
  • Validates plan-vs-implementation quality gates and edge-case coverage; emits a consolidated report and handoff decision.

Quick Start

Invoke /review {plan-slug} to trigger the eight-step review workflow.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a domain-aware code review for a release-critical pull request?▼

Domain-aware code review identifies and consolidates architectural findings, domain-specific reviewers, and test discipline feedback for a given plan and its implementation. It validates plan-vs-implementation quality gates and edge-case coverage to generate an auditable review report.

What is the best way to enforce quality gates after passing implementation validation?▼

Enforcing quality gates after implementation validation involves spawning specialized review agents across four pillars: architecture, tests, wiring, and cross-validation. This ensures comprehensive edge-case coverage and produces a consolidated report with a handoff decision.

How do I check if my plan-vs-implementation alignment meets rigorous quality standards?▼

Checking plan-vs-implementation alignment requires measuring implementation against the original plan across architecture, tests, wiring, and cross-validation pillars. This process detects edge-case coverage gaps and emits an auditable review report with a pass or fail handoff decision.

Can I consolidate architectural findings and test discipline feedback into a single report?▼

Yes, consolidating architectural findings and test discipline feedback is achieved by generating domain-aware reviewers that analyze the implementation. These specialized agents consolidate their findings into a single, auditable report for release-critical pull requests.

When do I need to trigger an eight-step review workflow for code quality?▼

An eight-step review workflow is needed when a release-critical pull request requires a deeper, domain-aware review after passing implementation gates. It ensures rigorous measurement across architecture, tests, wiring, and cross-validation pillars.

How does cross-validation improve code review for plan-driven development?▼

Cross-validation improves plan-driven development review by verifying the implementation against the plan across multiple specialized agents. This ensures edge-case coverage and generates an auditable report with a clear handoff decision.