devpilot-issue-triagelisted

# Triage GitHub Issue Backlog (Read-Only) ## Files in this skill | File | When to load | |---|---| | `references/bucket-rubric.md` | Step 2 — assigning a bucket. Rubric + counter-examples for each of the 6 buckets. | | `references/draft-comments.md` | Step 4 — exact wording for `needs-info`, `duplicate`, `stale` draft comments. | | `references/report-template.md` | Step 5 — the exact markdown skeleton for the output file, including the `devpilot-resolve-issues` handoff footer. | ## Overview End-to-end loop that takes the open-issue backlog of one GitHub repo and produces a single local markdown report classifying each issue, drafting follow-up actions, and (for `ready-to-fix` only) deep-diving into the code. **Nothing is posted to GitHub.** The user is the one who decides whether to act on the report. **Core principle:** Read-only against GitHub. Every proposed mutation lives in the report as a draft. Anything else turns this skill into a half-baked `devpilot-resolve-issues` and breaks the boundary that makes triage safe to run unattended. ## When NOT to Use - Creating new issues from a fresh code scan → `devpilot-scanning-repos`. - Actually fixing the `ready-to-fix` shortlist → hand the report to `devpilot-resolve-issues`. - Reviewing a PR the user already opened → `devpilot-pr-review`. - A single ad-hoc bug report — just discuss it directly, no triage report needed. ## The 6 Buckets (exhaustive — pick exactly one) | Bucket | Meaning | |---|---| | `ready-to-fix` | C