review-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.

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.

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.

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.

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.