phase-review

Audit Git changes, build results, and exit criteria for project phases.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/chy5301/cc-plugins --skill phase-review-chy5301
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-review
Source: https://github.com/chy5301/cc-plugins/tree/main/structured-workflow/skills/phase-review
Command: npx skills add https://github.com/chy5301/cc-plugins --skill phase-review-chy5301

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of reviewing and auditing completed project phases, ensuring quality, compliance, and process integrity without manual effort.

Core Features & Use Cases

  • Change and Quality Audit: Analyzes Git changes and compares them against task plans and status reports to identify discrepancies and inconsistencies.
  • Verification and Validation: Executes build and test procedures to confirm phase readiness according to predefined standards.
  • Use Case: When a development team completes a project phase, apply this Skill to review all modifications, verify successful builds, and ensure exit criteria are met before proceeding.

Quick Start

Ask the AI to review the latest project phase to ensure all tasks are completed, changes are justified, and standards are adhered to.

Frequently Asked Questions about phase-review

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

FAQPage Schema
How do I automate phase review and exit criteria verification for completed project phases?

Automated phase review validates project readiness by auditing code changes, verifying build and test results, and checking exit criteria adherence. It analyzes version control logs and configuration files to ensure phased delivery quality without manual effort.

What is the best way to audit Git changes against task plans and status reports?

Auditing Git changes against task plans involves comparing version control logs with status reports to identify discrepancies and inconsistencies. This change analysis ensures completed modifications match the predefined project scope and quality assurance standards.

Can I use this project review process for build verification and test result validation?

Project review supports build verification by executing build and test procedures to confirm phase readiness. It validates testing outcomes against predefined standards to ensure modifications meet quality compliance before proceeding to the next delivery phase.

Do I need version control logs and configuration files to perform a phase audit?

Phase audit requires version control logs and configuration files as input to analyze code modifications and verify exit criteria. These inputs provide the necessary data to audit changes, justify modifications, and ensure process integrity.

When should I not use an automated phase audit for project workflow validation?

Automated phase audit is not suitable when version control logs, configuration files, or testing outcomes are unavailable for analysis. It requires structured project phases with predefined exit criteria and standardized build verification procedures to function correctly.