clear-issueslisted
Install: claude install-skill rodlunt/claude-guardrails
# Clear issues
Triage a backlog of GitHub issues with the goal of moving as many as possible from open to closed in one focused session. Lean sequential by default; reach for parallel only when issues genuinely touch disjoint parts of the codebase.
## Procedure
### 1. Survey
Run `gh issue list --state open --json number,title,labels,body,createdAt,updatedAt --limit 100` to pull the full backlog. For any issue under serious consideration, also fetch comments via `gh issue view <N> --comments`. Comments often carry the actual blocker or the "actually we decided X" thread that the body never got updated for.
Sort each open issue into ONE bucket:
- **Close-without-code:** obsolete, duplicate, won't-do, or already-resolved-by-other-work.
- **Trivial:** small, contained, single-PR-sized, low risk.
- **Bundleable:** several related issues that share files or domain logic; one grouped PR closes many.
- **Standalone substantive:** real work, needs its own PR but doesn't naturally bundle.
- **Needs-discussion:** scope or design is unclear; cannot start without a decision.
- **Blocked:** depends on an external repo, decision, or vendor.
Open ages matter: an issue idle for 12+ months is more likely to be obsolete than one from last week. Surface the age in the bucket assignment.
### 2. Quiz the user, one question per turn
Do NOT propose the whole strategy upfront. Walk through the buckets in priority order, asking ONE focused question at a time. Quiz examples:
- For each Close-