What problem does it solve? When a repository has several open pull requests, merging them in the wrong order causes cascading rebases and merge conflicts across the whole queue. This Skill analyzes every open PR, builds a file-overlap matrix, and recommends a merge sequence that minimizes total rework for all authors. ## Core Features & Use Cases - Blast-radius ranking: Computes how many other open PRs each PR overlaps with, so the PR that disturbs the fewest others merges first, with staleness and size as tiebreakers only. - Semantic collision detection: Reads the actual diffs of overlapping PR pairs to distinguish incidental adjacency from likely logic collisions that could merge cleanly but be wrong. - Stack and severity awareness: Honors stacked-PR chains (parent before child, with restack steps) and promotes PRs linked to critical-severity issues ahead of the queue. - Snapshot management: Writes advisory reports under .claude/tmp/pr-triage/ with subcommands to list, open, and clean past runs, plus repeat-run mode that only re-analyzes changed PRs. - Use Case: You have six open PRs, several branched from the same commit, and need to know which to merge first. Run the triage to get a ranked sequence with per-PR rationale, conflict warnings, and linked-issue context. ## Quick Start Ask the assistant to triage the open pull requests on this repository and recommend a merge order.