Work on Repeat
Menu

Example routine

Stale pull request review

Find pull requests losing momentum, name what blocks each one, and propose the next action.

Use this routine

Suggested rhythm

Weekly

0 9 * * 4

America/Los_Angeles

Expected result

A stalled-work report listing each quiet pull request, what blocks it, who owns the block, and a proposed next step.

Built for

Engineering

Works with

  • GitHub

What the routine does

List open pull requests in the connected repository {{repository}} that have had no activity for {{staleDays}} days. For each, determine what it is waiting on — review, changes, CI, or a decision — name the person or check blocking it, and propose one concrete next action. Do not merge, close, or comment unless the tool for that action is explicitly approved.

Inputs

  • Repository{{repository}}

    The repository whose pull requests to review.

    Example: acme/web-app

  • Stale after (days){{staleDays}}

    Days without activity before a pull request counts as stale.

    Example: 5

Required MCP capabilities

  • Read repository pull requests
  • Read CI status

Permission boundary

Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.

More engineering routines