gh-stale-issueslisted

# Stale Issues Triage open issues by age and activity. Groups into buckets with a suggested action per issue. Useful before a release, after a period of heavy development, or when the issue list has drifted into noise. Triggered by: `/gh-stale-issues`, "stale issues", "triage issues", "clean up issues", "issue cleanup". Requires `gh` CLI authenticated. ## Steps ### 1. Fetch open issues ```bash gh issue list --state open --limit 200 --json number,title,createdAt,updatedAt,labels,assignees,comments,author ``` If the repo has 200+ open issues, note the cap and ask whether to paginate. ### 2. Classify by activity For each issue, compute: - **Age** — days since `createdAt` - **Inactivity** — days since `updatedAt` (last event: comment, label, assignment, etc.) - **Author response** — did the issue author comment after the initial post? (approximated by checking if `author` appears in later comments) ### 3. Group into buckets **No activity (90+ days):** Issues nobody has touched in 3 months. Likely abandoned or superseded. Suggest: close with a "stale — closing for inactivity, reopen if still relevant" comment, or label `wontfix`. **No author response (30+ days):** Issues that received a response (question, request for repro, etc.) but the original author hasn't replied. Suggest: ping author or close with "closing for no response." **Needs labels:** Issues with no labels at all. Hard to search, sort, or prioritize unlabeled issues. Suggest: add at least one label (`bu