review

Generate a structured review report anchored to PRD success criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill review-amodelandme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/amodelandme/skill-tree-dotnet/tree/main/.claude/skills/review
Command: npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill review-amodelandme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The final HITL gate ensures that no change reaches the remote without a formal, criteria-backed review, preventing drift between implementation and project standards.

Core Features & Use Cases

  • Anchors the review to PRD success criteria or chore intents and compiles evidence from diffs, tests, and docs.
  • Performs a drift and coverage check across the change set and surfaces gaps before pushing.
  • Produces a decision-ready report that becomes the PR body on push, guiding reviewers and gatekeepers.

Quick Start

Run the review command on the feature branch after completing the AFK loop to generate the final gate report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I validate PRD success criteria against current branch changes before pushing?

To validate PRD success criteria, the review process identifies coverage gaps by assessing the current diff against documentation and tests, ensuring implementation aligns with project standards before pushing.

What is a HITL gate in a CI-CD pull request workflow?

A HITL gate in a CI-CD pull request workflow is a final human-in-the-loop review checkpoint that anchors to PRD criteria, preventing drift between implementation and standards before changes reach the remote.

How do I generate a structured PR review report from a feature branch diff?

To generate a structured PR review report, run the review command on the feature branch after completing the AFK loop, which compiles evidence from diffs, tests, and docs into a decision-ready output.

Does the pre-push review check for documentation and test coverage gaps?

Yes, the pre-push review performs a drift and coverage check across the change set, assessing the diff against documentation and tests to surface gaps before the final push decision is stated.

Can I use this review gate for chore intents instead of formal PRD criteria?

Yes, the review gate can anchor its validation to either formal PRD success criteria or chore intents, compiling the necessary evidence from the diff to produce a decision-ready report.

What is the best way to prevent implementation drift before merging a pull request?

The best way to prevent implementation drift is to enforce a final HITL gate that validates branch changes against PRD criteria, tests, and documentation, generating a structured report for PR body generation.