Manage open-source GitHub issue backlogs (especially PrefectHQ/prefect) in batches. Use for backlog cleanup days, stale review, duplicate pruning, missing-info follow-up, and prioritized queue curation across many open issues.
Use this skill for batch backlog work, not for deep triage of a single new issue.
Use two passes by default:
close-not-planned and close-duplicate candidates.Do not finalize close actions from Pass 1 alone.
For Pass 2, require explicit evidence:
low, medium, high)If evidence is weak or mixed, downgrade close to:
needs:detailsneeds:mrestatus:stalekeep-openUI replatform exception:
ui/) and the React replatform (ui-v2/).ui-v2 is GA.ui/, ui-v2/, or both.keep-open (or status:stale only if explicitly desired by maintainers).Use focused searches:
gh issue list --repo PrefectHQ/prefect --search "is:open is:issue no:assignee sort:updated-asc" --limit 100
gh issue list --repo PrefectHQ/prefect --search "is:open is:issue label:status:stale sort:updated-asc" --limit 100
gh issue list --repo PrefectHQ/prefect --search "is:open is:issue label:bug -label:needs:mre sort:updated-asc" --limit 100
gh issue list --repo PrefectHQ/prefect --search "is:open is:issue label:needs:details sort:updated-asc" --limit 100
Choose exactly one primary action per issue:
keep-open: still actionable, no immediate label change neededneeds:details: missing context blocks progressneeds:mre: bug report lacks minimal reproducible examplestatus:stale: inactive and low-signal, not exemptclose-duplicate: close with canonical issue linkclose-not-planned: close with concise reason when clearly out of scope or no longer actionableFor every close candidate, produce this mini-record before execution:
issue: number + titleclaim_to_verify: why it appears closablecurrent_state_check: does claim still hold today?evidence_links: specific referencescounterevidence: any signal to keep openrecommended_action: final action after deep-diveconfidence: low/medium/highOnly use labels that exist in this repo. Key labels for backlog work include:
needs:detailsneeds:mrestatus:staleneeds:triagequestionbugenhancementgood first issueblockedstatus:exemptVerify labels before applying changes:
gh label list --repo PrefectHQ/prefect --limit 30
Missing details:
Thanks for opening this. We need a bit more detail before we can move this forward:
- expected behavior
- actual behavior
- exact steps to reproduce
Missing MRE:
Thanks for the report. Please share:
1) a minimal reproducible code sample,
2) full traceback/error text,
3) output of `prefect version`.
Duplicate close:
Closing as a duplicate of #<issue-number> so discussion stays in one place.
If this is materially different, tag me and comment with details; we can reopen.
ui-v2 GA unless there is a strong non-UI reason (for example, duplicate with active canonical issue).