pre-merge-review

Coordinate pre-merge external review by selecting a reviewer and delivering branch diff, commit log, and plan context.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/anortham/razorback --skill pre-merge-review-anortham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-merge-review
Source: https://github.com/anortham/razorback/tree/main/skills/pre-merge-review
Command: npx skills add https://github.com/anortham/razorback --skill pre-merge-review-anortham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates external pre-merge reviews by coordinating reviewer selection, diff/context delivery, and plan verification to ensure code changes are reviewed and tracked before merging.

Core Features & Use Cases

  • End-to-end pre-merge review orchestration: selects a reviewer (codex / gemini / claude), packages the branch diff, commit log, and plan path, and routes them through the verification pipeline.
  • Structured findings & traceability: normalizes external-review findings into the shared schema for PR summaries and automated morning reports.
  • Plan-guided execution: enforces pre-merge gate checks and emits blockers or required follow-ups based on verification outcomes.

Quick Start

Invoke the pre-merge-review skill on the current branch diff and plan, then process reviewer findings through the verification protocol.

Frequently Asked Questions about pre-merge-review

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

FAQPage Schema
How do I coordinate external pre-merge code reviews across different AI models?

External pre-merge code review orchestration selects a reviewer like codex, gemini, or claude, packages your branch diff, commit log, and plan context, then routes them through a verification pipeline to ensure changes are tracked before merging.

What is the best way to normalize AI reviewer findings for automated pull request summaries?

Normalizing external review findings into a shared schema standardizes AI reviewer outputs, enabling consistent downstream processing for PR narration, discovery, and automated morning reports without manual formatting.

How do I enforce pre-merge gate checks based on a verification plan?

Plan-guided execution enforces pre-merge gate checks by evaluating verification outcomes and emitting blockers or required follow-ups, ensuring code changes meet specified branch-gate scope and model routing requirements before merging.

Does pre-merge review require specific MCP servers to function?

Yes, pre-merge review assumes configured Julie MCP and Goldfish MCP servers are available, along with a plan that specifies model routing, branch-gate scope, and required verification steps to orchestrate the external review pipeline.

Can I use branch diffs and commit logs to trigger automated code review before merging?

Yes, the skill packages the current branch diff, commit log, and plan path, delivering them to a chosen external reviewer tool to execute pre-merge verification and generate structured findings for downstream tracking.