check-prs

Scan open pull requests and identify stale review requests needing maintainer action.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill check-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-prs
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/check-prs
Command: npx skills add https://github.com/gittower/git-flow-next --skill check-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers quickly understand which open pull requests are waiting on review, which need author follow-up, and which have exceeded the response window.

Core Features & Use Cases

  • Open PR Scanning: Lists open pull requests and skips drafts.
  • Review Window Assessment: Checks the latest maintainer review, author activity after review, and how long each PR has been waiting.
  • Actionable Reporting: Produces a sorted status table with the next recommended action, and can optionally draft or post reminder comments for nearly lapsed PRs.
  • Use Case: A maintainer can run this Skill before a release or triage session to identify which PRs are ready for takeover, follow-up, or immediate review.

Quick Start

Ask the assistant to scan open pull requests and report which ones need review attention or have lapsed against the response window policy.

Frequently Asked Questions about check-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify stale pull requests that are blocking merges?

You identify stale pull requests by scanning open PRs, inspecting review history, and comparing author activity after the latest maintainer review to track how long each PR has been waiting.

What is the best way to triage open GitHub pull requests for maintainer action?

Triage open GitHub pull requests by scanning them, skipping drafts, and assessing the review window to produce a sorted status table with the next recommended maintainer action.

Can I automatically post reminder comments for lapsed PRs?

Yes, you can automatically post reminder comments for lapsed PRs by optionally drafting or posting issue-comments directly to GitHub pull requests that have exceeded the response window.

Does this PR triage workflow skip draft pull requests?

Yes, this PR triage workflow skips draft pull requests entirely, focusing only on listing open pull requests that require maintainer review and tracking their active review windows.

How do I track the response window for active GitHub PR workflows?

You track the response window for active GitHub PR workflows by checking the latest maintainer review, comparing author activity after that review, and assessing how long the PR has been waiting.

When should I consider a takeover decision for a stale pull request?

You should consider a takeover decision for a stale pull request when it has exceeded the response window and lacks author activity after the latest maintainer review, blocking merges before a release.