Check PRs
SkillDev toolsScan open PRs for stale review requests and report which need action
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Check PRs skill
What this skill tells your AI
The instructions your AI receives, as published by gittower/git-flow-next in .claude/skills/check-prs/SKILL.md and read by ahel’s review.
Scan all open pull requests and report where each stands against the review response window policy in CONTRIBUTING.md. Read-only by default — run manually whenever you want an overview. Posting reminders is optional and gated.
Arguments
/check-prs
Instructions
1. Gather Open PRs
gh pr list --state open --json number,title,author,updatedAt,reviewDecision,isDraft
Skip drafts.
2. Assess Each PR
For each PR, fetch reviews and comments and determine:
- Latest maintainer review and its verdict + date
- Author activity since: commits pushed, comments, or review replies after that review (any activity resets the window)
- Days waiting: since the review if unanswered, else since last maintainer activity
Classify:
| Status | Meaning |
|---|---|
awaiting review | No maintainer review yet — action is on us |
changes requested — in window | Author has < 7 days left to respond |
changes requested — window lapsed | ≥ 7 days, no author response — takeover eligible |
author responded | Author replied/pushed — action is on us to re-review |
approved | Ready to merge |
3. Report
Output a table sorted by urgency (lapsed first, then author-responded, then awaiting review):
| PR | Title | Author | Status | Days | Next action |
|----|-------|--------|--------|------|-------------|
| #93 | ... | @user | window lapsed | 9 | /takeover-pr 93 |
| #95 | ... | @user | author responded | 2 | /follow-up-review 95 |
| #96 | ... | @user | awaiting review | 4 | /handle-pr 96 |
Include concrete evidence for lapsed PRs (review date, last author activity) so the takeover decision is verifiable.
4. Optional: Reminders
For PRs in-window but close to lapsing (5–6 days), offer to post a friendly
reminder comment. Draft the comment, show it, and post only after user
confirmation (mcp__github__add_issue_comment). Never post reminders
unprompted.
Signals
- GitHub stars
- 439
- Forks
- 28
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
check-prs- Source
- github.com/gittower/git-flow-next