merge-review

Analyze pending fleet worktree merges and surface conflicts without merging.

820|78|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SethGammon/Citadel --skill merge-review-sethgammon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-review
Source: https://github.com/SethGammon/Citadel/tree/main/skills/merge-review
Command: npx skills add https://github.com/SethGammon/Citadel --skill merge-review-sethgammon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fleet merge arbitration helps teams review pending worktree merges, detect conflicts between branches, and propose a safe merge order without performing any merges automatically.

Core Features & Use Cases

  • Read the merge queue from .planning/telemetry/merge-check-queue.jsonl and track pending branches for review.
  • Detect overlapping file changes across branches and identify potential conflicts to surface early.
  • Propose a safe merge order and surface reconciliation plans to guide human decisions.
  • Update the queue to reflect reviewed or merged branches and provide guidance on cleanup of merged worktrees.
  • Generate a clear, actionable report that supports autonomous workflows while preserving codebase safety.

Quick Start

Run /merge-review to process all pending branches and generate a report.

Frequently Asked Questions about merge-review

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

FAQPage Schema
How do I detect merge conflicts across multiple git worktree branches before merging?

To review pending worktree merges, run the merge-review command. It reads the merge queue, computes a safe merge order by analyzing branch diffs, and returns a structured report detailing conflicts and reconciliation plans.

What is a safe merge order and how does it help manage a git merge queue?

Yes, this merge arbitration process is designed for autonomous workflows. It processes pending branches automatically and generates actionable reports with reconciliation plans, while preserving codebase safety by avoiding automatic merges.

How do I track pending git worktree branches for review without auto-merging them?

After reviewing queued branches, the system updates the merge queue to reflect reviewed or merged statuses. It also provides guidance on cleaning up merged worktrees to maintain a tidy and efficient development environment.

Can I automate git worktree cleanup after branches are merged from the queue?

Yes, after updating the queue to reflect merged branches, the system provides guidance on cleaning up merged worktrees. This ensures the workspace remains organized and ready for subsequent merge review cycles.