Stale pull request triage on a schedule

A Crongent routine can sweep every repo you scope it to on a schedule, list pull requests with no activity for N days, work out why each one is stuck, and leave a short nudge on the PR or post a digest. You set the threshold, tone and which repos count.

The problem

Stale PRs rot: merge conflicts pile up, context is lost and work gets redone. Static bots close PRs blindly; a person has to read each one to know if it is blocked or abandoned.

How to set it up in Crongent

  1. Create a weekly routine scoped to your repos.
  2. Tell the agent the idle threshold and how to nudge (comment, label, or digest only).
  3. Turn on writes and allow only the comment tool, so it can nudge but never merge or close.
  4. Read the transcript to see every PR it looked at and why.

Example routine

Name
Stale PR sweep
Trigger
Weekly, Monday 9:00
Model
anthropic/claude-haiku-5.5
Instructions
List open PRs with no activity in 7 days. For each, say in one sentence what is blocking it and @-mention the author with a friendly nudge.

Who uses it

Frequently asked questions

Can it close stale pull requests?
No. Crongent agents cannot merge or close pull requests. Routines are read-only by default; with writes on they can comment and edit issues.

Related use cases