two-stage-review

Verify code against specifications and assess quality in two phases.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/disciplin-run-org/jjstack --skill two-stage-review-disciplin-run-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: two-stage-review
Source: https://github.com/disciplin-run-org/jjstack/tree/main/skills/two-stage-review
Command: npx skills add https://github.com/disciplin-run-org/jjstack --skill two-stage-review-disciplin-run-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the code review process by splitting it into two distinct phases—verification against the specification and assessment of code quality—reducing bugs and improving code standards.

Core Features & Use Cases

  • Two-Stage Review Process: Separates spec compliance checks from quality assessments to catch different types of issues.
  • Workflow Automation: Guides reviewers through a structured process, ensuring thorough evaluations.
  • Use Case: Ideal for reviewing complex feature implementations or PRs where both correctness and maintainability are critical, such as verifying that code matches detailed specifications before evaluating its robustness.

Quick Start

To perform a specification pass, provide the spec and diff to a subagent, then follow with a quality review to assess the code's integrity and standards.

Frequently Asked Questions about two-stage-review

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

FAQPage Schema
How do I perform a structured PR review for complex feature implementations?

Structured PR review separates spec compliance checks from code quality assessments to catch different types of issues. This two-stage process ensures thorough evaluations by first verifying correctness against specifications, then evaluating robustness and maintainability.

What is a two-stage code review process and when is it needed?

A two-stage code review verifies adherence to specifications before assessing code quality. It is needed for complex development workflows where both correctness and maintainability are critical, reducing bugs by evaluating spec compliance and code integrity separately.

How do I verify code matches detailed specifications before evaluating quality?

To verify code matches specifications, provide the spec and diff to a subagent for a specification pass. Follow this with a quality review to assess the code's integrity and standards, ensuring the implementation is correct before checking robustness.

Does separating spec verification from quality assessment improve bug prevention?

Separating spec verification from quality assessment improves bug prevention by isolating correctness checks from maintainability checks. This structured evaluation ensures specific issues are caught independently, preventing bugs and elevating overall code standards.

Can I automate workflow guidance for multi-phase code reviews?

Workflow automation for multi-phase code reviews guides reviewers through a structured process, ensuring thorough evaluations. It facilitates the separation of spec compliance and quality assessment without manual tracking, streamlining the entire PR review.

What are the limitations of combining spec compliance and code quality checks?

Combining spec compliance and code quality checks risks overlooking specific issues because different types of bugs require distinct evaluation stages. Separating them ensures thorough evaluations, preventing bugs that a single-pass review might miss.