review-merge-readiness

Review git diffs against requirements and produce a merge readiness verdict.

339|58|Updated Jan 10, 2026

Search Tags:#code-review #audit-trail #production-readiness #git-diff #merge-readiness #baselining

Ready to run

npx skills add https://github.com/Heyvhuang/ship-faster --skill review-merge-readiness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-merge-readiness
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/review-merge-readiness
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill review-merge-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill standardizes code reviews to ensure baseline alignment with plans and production readiness, surfacing issues before merges and enabling auditable decisions.

Core Features & Use Cases

Structured review: compares implemented changes against plan/requirements using git diffs.
Issue scoring: reports Critical, Important, and Minor issues with actionable fixes.
Merge readiness verdict: provides a clear Yes/No/With fixes assessment and recommended next steps.
Use Case: after completing a major feature, run a review before merging to main to ensure acceptance criteria are met.

Quick Start

Run the review against the current HEAD and a baseline to generate an actionable report that guides merge decisions.

Frequently Asked Questions about review-merge-readiness

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

FAQPage Schema

How do I perform a structured code review for merge readiness?▼

Merge readiness reviews compare implemented changes against baseline requirements using git diffs to surface issues. This structured review collects implementation details, plans, and diff evidence to produce a prioritized issues list and a final merge verdict.

What is the best way to gate a feature branch before merging to main?▼

Gating a feature branch before merging requires validating baseline alignment and production requirements. A structured review generates traceable evidence, scores issues by severity, and provides a clear Yes, No, or With fixes verdict to guide the merge decision.

How does a git diff audit trail work for pre-merge code reviews?▼

A git diff audit trail works by comparing current HEAD against a baseline to verify production readiness. It enforces consistent criteria by collecting what was implemented, plan requirements, and diff evidence to ensure traceable and auditable merge decisions.

Can I use this structured review for batch reviews across multiple feature completions?▼

Yes, structured reviews support batch reviews across multiple feature completions and pre-merge gates. The review applies consistent criteria by evaluating git diffs and plan requirements, producing actionable issue fixes and a merge readiness verdict for each batch.

What do I need to provide to generate a merge readiness verdict?▼

To generate a merge readiness verdict, you need to provide the current HEAD, a baseline for comparison, and any plan or requirements documents. The review uses these inputs to analyze git diffs and produce a prioritized list of Critical, Important, and Minor issues.