post-merge-review

Validate merged changes against original scope with parallel functional, security, and quality reviews.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill post-merge-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-merge-review
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/phases/post-merge-review
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill post-merge-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents merged code from advancing when the delivered work does not fully match the original scope, by running coordinated functional, security, and quality validation after integration.

Core Features & Use Cases

  • Three-architect parallel validation: Runs functional completeness, security depth, and code-quality review concurrently against the original scope.
  • Requirement-level zero-tolerance: Produces per-requirement PASS/FAIL evidence and fails the gate if any item is missing or incorrect.
  • Fix-and-retry recovery loop: Automatically triggers an executor to remediate all failing items and re-runs the review up to a configurable iteration cap.
  • Audit-friendly outputs: Writes complete architect outputs (including all iterations) to a review artifact file for later inspection.

Quick Start

Run a thorough or epic workflow and ensure this post-merge review phase is included between the integration phase and completion guard.

Frequently Asked Questions about post-merge-review

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

FAQPage Schema
How do I enforce zero-tolerance code review after merging changes?

Zero-tolerance code review after merging validates that integrated changes fully deliver the original scope by running parallel functional, security, and quality checks. It blocks workflow advancement unless all per-requirement evidence passes.

What is parallel multi-agent validation for post-integration quality gating?

Parallel multi-agent validation is a post-integration quality gating mechanism where functional, security, and code-quality architects review merged changes concurrently. It ensures requirement-level completeness before allowing workflow progression.

How do I automate fix-and-retry loops for failing security and quality checks?

Automate fix-and-retry loops by triggering an executor to remediate failing items after a review. The system re-runs validation up to a configurable iteration cap until zero failures remain or the limit is reached.

Does post-merge review work with epic and thorough workflow orchestration modes?

Post-merge review works with epic and thorough workflow orchestration modes by inserting quality gating between the integration phase and completion guard. It applies per-requirement PASS/FAIL checklists to verify scope delivery.

Can I generate audit-friendly artifacts from multi-agent code review iterations?

Yes, you can generate audit-friendly artifacts from multi-agent code review iterations. The system writes complete architect outputs, including all fix-and-retry cycles, to a review artifact file for later inspection.

Why does my workflow not advance after a merged code review?

Your workflow does not advance because the zero-tolerance criteria detected a FAIL in the per-requirement checklist. State and evidence updates only advance the workflow when a VERDICT: PASS is achieved.