review

Analyze code diffs to determine a post-verify QA gate outcome.

Updated Jan 4, 2026

Search Tags:#documentation #qa #review #diff #gate #acceptance

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill review-yeachan05

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/review
Command: npx skills add https://github.com/YeaChan05/Remittance --skill review-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable gate for post-change verification, ensuring diffs align with specifications, risk considerations, and required documentation.

Core Features & Use Cases

Automated assessment of diffs against acceptance criteria and design docs.
Generation of a clear gate decision (pass, partial-pass, or fail) with actionable findings.
Verification of documentation synchronization and risk flags for release readiness.

Quick Start

Run the review on the latest diff and record a pass, partial-pass, or fail with notes.

Frequently Asked Questions about review

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

FAQPage Schema

How do I run a post-change QA gate on a code diff?▼

A post-change QA gate evaluates code diffs against acceptance criteria, documentation, and risk flags. It outputs a structured gate decision of pass, partial-pass, or fail, along with actionable findings for release readiness.

What is a cross-diff validation gate for release readiness?▼

A cross-diff validation gate is a structured post-verify check ensuring code changes align with design specifications and documentation. It generates a clear pass, partial-pass, or fail decision with notes on document synchronization and risk assessment.

How do I verify documentation synchronization after a code change?▼

Verify documentation synchronization by running a post-change review gate that checks the diff against required docs. The gate explicitly validates document checks and flags any misalignment or missing updates needed for release readiness.

When do I need to use a structured QA gate instead of a standard code review?▼

You need a structured QA gate when code changes require cross-diff validation against acceptance criteria, documentation, and risk assessment. It enforces a defined failure route and clear pass/fail results rather than subjective review feedback.

What does a partial-pass gate decision mean for a code diff?▼

A partial-pass gate decision means the code diff met some but not all acceptance criteria or documentation checks. It includes actionable findings and a defined failure route to guide remaining fixes before achieving full release readiness.