On a weekly schedule, scans open issues, works out why each one is quiet, posts a targeted nudge, and flags for closure the ones that have been quiet far too long. Advisory only: it never closes anything. Set your repository on the Clone step after importing.
- Identifier
stale-issue-reaper- Version
- 1.0.1
- Steps
- 3
- Triggers
- 1
- issues
- maintenance
- scheduled
- hygiene
- automated
When it runs
schedule.weekly- Schedule
- Every Tuesday at 09:00 UTC
0 9 * * 2 - Timezone
- UTC
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01Weekly Schedule (Tuesday 09:00 UTC)
triggerThe event that starts the run.
- 02Clone Repository ⚠️ SET YOUR REPO
git.cloneShallow-clones the repository at the right ref.
- 03Scan & Nudge Stale Issues
agent.runOne agent works the task with its toolkit.
The agent
Stale Issue Reaper
- Base type
- Senior Developer
- Temperature
- 0.2
- Max iterations
- 45
- Tools
- 8
Git provider · 4
list_issuesList Issues · readcreate_issue_commentCreate Issue Comment · writeadd_labelsAdd Labels · writeremove_labelRemove Label · write
Filesystem · 2
read_fileRead File · readlist_dirList Directory · read
Code search · 1
code_searchCode Search · read
Status · 1
update_statusUpdate Status · write
Related playbooks
Issue Triage
Labels new issues as bug, feature, question, docs, or task and checks for missing info.
Auto Root Cause Analysis
Investigates bug-labeled issues, traces the root cause in code, and posts the analysis with a fix.
Duplicate Issue Detector
Compares new issues against existing open ones and links likely duplicates.