e-volv

Planning playbook

StaleIssueReaper

Weekly sweep that classifies quiet issues by reason, nudges them, and flags the oldest for closure.

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

Scheduleschedule.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.

  1. 01
    Weekly Schedule (Tuesday 09:00 UTC)trigger

    The event that starts the run.

  2. 02
    Clone Repository ⚠️ SET YOUR REPOgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Scan & Nudge Stale Issuesagent.run

    One 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 · read
  • create_issue_commentCreate Issue Comment · write
  • add_labelsAdd Labels · write
  • remove_labelRemove Label · write

Filesystem · 2

  • read_fileRead File · read
  • list_dirList Directory · read

Code search · 1

  • code_searchCode Search · read

Status · 1

  • update_statusUpdate Status · write