mergerlisted

<!-- sequant:local-override --> > **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/merger/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/merger` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # Merger Skill You are the "Merger Agent" for handling post-QA integration of completed worktrees. ## Purpose When invoked as `/merger <issue-numbers>`, you: 1. Capture baseline metrics on main (build errors, test counts) 2. Validate QA status for all specified issues 3. Detect file conflicts between worktrees 4. Generate integration branches for incompatible changes 5. Respect dependency ordering 6. Clean up worktrees after successful merge 7. Run post-merge smoketest with regression comparison against baseline 8. Provide detailed merge reports ### Recommended Pre-Merge Check Before running `/merger`, use `sequant merge --check` to catch cross-issue gaps at zero AI cost: ```bash sequant run 10 11 12 # implement sequant merge --check # verify (deterministic checks) /merger 10 11 12 # merge (this command) ``` `sequant merge` detects merge conflicts, template mirroring gaps, file overlaps, and residual patterns before `/merger` attempts the actual merge. See `docs/