cleanup-issues-prsworkflow★308
madeye/meow-rs ↗What it does
Triage GitHub issues and PRs systematically
Best for
Recurring issue/PR backlog grooming when needs to flag fixed/stale/duplicate tickets and stuck PRs without manual review
Inputs
- · open GitHub issues (number, title, labels, updatedAt)
- · open GitHub PRs (number, title, author, updatedAt, isDraft)
- · optional args.apply flag to execute closes
Outputs
- · issue recommendations (action: close-fixed/close-stale/close-duplicate/comment/keep)
- · PR recommendations (action: merge-ready/needs-rebase/needs-review/superseded/stale-ping)
- · executed actions log (dry-run by default)
Requires
- · gh CLI (GitHub API)
- · pipeline orchestration
- · agent per issue/PR
Preconditions
- · gh CLI authenticated with repo access
Failure modes
- · GitHub CLI auth fails or repo not accessible
- · stale issue/PR state causes wrong recommendation
- · no open issues/PRs to triage (empty backlog)
Trust signals
- · 3-phase orchestration (Inventory, Triage, Apply)
- · Separate schemas for issue vs PR recommendations
- · Confidence scoring (high/medium/low) per recommendation
- · High-confidence closes only applied with args.apply=true