merge-review

A merge review reads the pending queue, performs diff analyses across branches, and identifies overlapping files to detect file-level conflicts before they are accepted. It outputs a structured report detailing the conflicts and necessary reconciliations.

The best way to determine a safe merge order is to assess per-branch risk levels for overlapping changes. A merge review evaluates the queue, identifies file-level conflicts, and proposes a structured sequence for merging branches to avoid integration failures.

Yes, you can automate reporting for multi-branch git worktree merges by running a merge review on the full queue. It assesses risk per branch and outputs a consolidated report with actionable recommendations for the entire pending fleet.

Yes, the merge review process specifically supports multi-branch scenarios where overlapping changes require reconciliation. It performs diff analyses to assess per-branch risk and surfaces reconciliation plans for the conflicting files.

To generate a merge report for a fleet of pending worktree merges, run the merge-review command on the full queue. It parses pending merges, analyzes diffs, detects conflicts, and outputs a consolidated report with a safe merge order.