What problem does it solve?
Teams triaging a backlog of open pull requests need a fast, consistent answer to "what is blocked and why" without manually reading every PR's checks and review state. This Skill turns a JSON export of open PRs into a blockers-first digest: which PRs are blocked (failing checks, requested changes, awaiting review, or stale), which are ready to merge, and a one-line count suitable for standup.
Core Features & Use Cases
- Blocker triage: Classifies each PR with explicit reasons such as failing checks, changes requested, awaiting review, or stale beyond 7 days.
- Ready-to-merge detection: Flags PRs as ready only when checks are explicitly passing and review is explicitly approved, treating missing fields conservatively.
- Standup summary line: Produces a one-line count (total, blocked, ready) an agent can post directly to standup.
- Bundled eval harness: Ships with an eval spec and three golden cases so the pipeline can be validated and regression-tested with run_evals.py.
- Use Case: Export your open PRs as JSON, run the pipeline, and paste the resulting digest into your daily standup to assign unblock actions.
Quick Start
Ask the agent to summarize the attached JSON export of open pull requests into a blockers-first standup digest listing blocked PRs with reasons and ready-to-merge PRs.