stale-prs

What this does

Asks the user for a repository (owner/repo), then fetches open PRs older than 7 days, groups them by age and draft status, and renders a categorized report.

Step 1: Get the repository

If the user didn't provide a repository name, ask for one in owner/repo format using AskUserQuestion.

Step 2: Fetch stale PRs

The gh CLI may not be on PATH directly - activate the user's tool manager first:

eval "$(/opt/homebrew/bin/mise activate zsh)" && \
gh pr list --repo <owner/repo> \
  --state open \
  --json number,title,url,author,createdAt,isDraft \
  --limit 100

Filter the results to only include PRs where createdAt is more than 7 days ago relative to today.

Step 2.5: Resolve Slack users — REQUIRED when Slack tools are available

This step is NOT optional when Slack tools are available. Do not skip it. The only case where you skip this step is when Slack tools (e.g., slack_search_users) are genuinely unavailable in the environment. If slack_search_users (or an equivalent) is in your tool list, you MUST run the lookup before formatting output — even for terminal/markdown output, because the display names come from Slack profiles, not GitHub.

Do not rationalize skipping this step ("it's just for terminal", "Slack lookup feels like overhead", "GitHub logins are close enough"). Those are exactly the wrong reasons. Run the lookup.

How to do the lookup:

• Search once per unique GitHub login (not per PR). Issue all lookups in parallel in a single tool-call batch — do not serialize them.
• Try the GitHub login first; if no match, try the author's full name from the GitHub API response.
• Build a mapping of GitHub login -> { slackId, displayName } (e.g., prichodko -> { slackId: "U0AJ0FEU6QL", displayName: "pavel" }).
• If a specific user can't be found in Slack, fall back to their GitHub login for that author only — but still do the lookup for everyone else.
• Only skip the entire step if Slack tools are not present in the environment at all. In that case, use GitHub logins for everyone.

The mapping is used in Step 3 to render author names. When the output is for terminal/markdown, use the Slack display name (e.g., @pavel). When the output will be posted to Slack, use Slack's mention syntax: <@U0AJ0FEU6QL> so the user gets a proper notification.

Step 3: Format the output

First, separate PRs into two top-level groups: Ready for review (non-draft) and Drafts. Within each group, bucket PRs by age: 1-2 weeks old, 2-4 weeks old, Over a month old.

Terminal / markdown output (default)

Use standard markdown. Links are [text](url), authors are @displayName.

### Ready for review

**1-2 weeks old**
- [Title of PR](url) - 10d - @pavel

### Drafts

**Over a month old**
- [Title of PR](url) - 45d - @dipree

Slack output (when posting to Slack)

When the user asks to send/post to Slack, use Slack's formatting syntax:

• Links: <url|text>
• Mentions: <@SLACK_USER_ID>
• Bold: *text*
• No markdown headers — use bold lines instead

*Ready for review*

*1-2 weeks old*
- <https://github.com/org/repo/pull/123|Title of PR> - 10d - <@U0AJ0FEU6QL>

*Drafts*

*Over a month old*
- <https://github.com/org/repo/pull/456|Title of PR> - 45d - <@U09JZNQKM3J>

Shared rules

• Age is shown as Xd (e.g., 10d)
• Within each bucket, sort oldest first
• Omit empty buckets and empty groups entirely
• Exclude bot PRs (author login starts with app/ — e.g., dependabot) from the detailed list. Instead, summarize them in a single line at the end, e.g.: "Plus 12 dependabot PRs that need attention (oldest: 63d)."
• End with a one-line summary: total count, how many are drafts, how many are bot PRs

If there are no stale PRs, say: "No PRs open longer than a week."