code-review

Automate two-stage code reviews for specification compliance and code quality.

3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/HankLiu447/SuperSpec --skill code-review-hankliu447
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/HankLiu447/SuperSpec/tree/main/skills/code-review
Command: npx skills add https://github.com/HankLiu447/SuperSpec --skill code-review-hankliu447

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end code reviews by validating specification compliance and code quality to prevent drift and defects.

Core Features & Use Cases

  • Two-Stage Review: Stage 1 Spec Compliance Review ensures alignment with requirements; Stage 2 Code Quality Review checks error handling, type safety, and maintainability.
  • Structured Checklists: Predefined criteria, tests, and evidence requirements for each review.
  • Workflow Integration: Fits subagent-driven development, post-implementation checks, and pre-merge validations.

Quick Start

Use the code-review skill to initiate a two-stage review of a new feature implemented by the subagents.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for spec compliance and quality assurance?

Automating code review for spec compliance requires a two-stage validation process that first checks alignment with requirements and then evaluates error handling, type safety, and maintainability to prevent drift and defects.

What is a two-stage code review process for subagent development?

A two-stage code review process for subagent development separates requirement validation from quality checks, using structured checklists and issue classifications to ensure post-implementation outputs meet predefined evidence requirements before merging.

How do I validate git diff outputs against project specifications?

Validating git diff outputs against specifications involves enforcing a spec compliance review stage that automatically checks implemented features against structured criteria and predefined tests to prevent requirement drift.

Can I use automated code review for pre-merge validation in TDD workflows?

Automated code review fits pre-merge validation and TDD workflows by running structured checklist validations on subagent-driven implementations, checking both spec compliance and code quality before integration.

What is the best way to enforce code quality checks in subagent-driven workflows?

The best way to enforce code quality in subagent-driven workflows is applying a structured second-stage review that classifies issues and evaluates error handling, type safety, and maintainability using predefined criteria and evidence requirements.

Does automated code review work without external dependencies or components?

Automated code review can operate without external dependencies or components, relying entirely on its internal two-stage review logic, structured checklists, and issue classification systems to validate spec compliance and code quality.