What problem does it solve? When a repository accumulates many open issues, deciding what to fix first, what to combine into one PR, what to close as moot, and what needs a human decision is manual and error-prone. This Skill analyzes the open issue queue and produces an advisory fix plan instead of a flat ranking. ## Core Features & Use Cases - Relationship graph: Detects file overlap, symbol collisions, declared and semantic dependencies, supersession, and duplicates between issues. - Per-issue dispositions: Assigns WORK, GROUP, CLOSE-MOOT, NEEDS-DECISION, DEFER, STACK, or HOLD to every issue, then orders workable units by dependency, severity, and effort. - Snapshot and label sync: Writes a scoped report under .claude/tmp/issue-triage/ and can sync a status: needs-decision label to GitHub after confirmation. - Use Case: A maintainer with 15 open issues runs a triage to learn that two issues rewrite the same function and should ship as one PR, one is mooted by another fix, and one is blocked on a policy decision. ## Quick Start Ask the assistant to triage the open GitHub issues in this repository and recommend which to fix first, which to group, and which need a decision.
