status

Generate a consolidated PR dashboard with review state, findings, and blockers.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill status-auerbachb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/status
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill status-auerbachb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual effort of inspecting multiple pull requests across a repository by aggregating review states, unresolved findings, check-run results, and merge readiness into a single dashboard so maintainers can quickly identify blockers and next actions.

Core Features & Use Cases

  • Consolidated PR overview: Lists open PRs with titles, reviewer assignments, HEAD SHA, last update time, and a concise state (Clean, Has findings, Review pending, Rate-limited).
  • Automated review state collection: Uses per-PR helper scripts to fetch reviews, inline comments, unresolved threads, check-runs, and bot-generated findings to classify readiness.
  • Merge gate verification: Invokes the repository's merge-gate helper to determine merge-readiness and surface missing requirements or rate-limit conditions.
  • Session cross-checks: Optionally enriches the dashboard with active agent state, CR quota, and phase assignments when a session-state file exists.
  • Use case: Quickly answer "which PRs are merge-ready and which are blocked by findings or CI?" for triage and release planning.

Quick Start

Show me a dashboard of all open PRs in this repository with reviewer, state, unresolved findings, and blockers.

Frequently Asked Questions about status

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

FAQPage Schema
How do I consolidate open pull request review states and blockers into a single dashboard?

A PR dashboard aggregates reviewer statuses, unresolved threads, check-run results, and merge readiness across up to 50 open pull requests, classifying each with a concise state like Clean, Has findings, or Review pending.

Can I check merge readiness for multiple GitHub pull requests at once?

Merge readiness is verified by invoking a merge-gate helper script that checks per-PR state, surfacing missing requirements or rate-limit conditions across all open pull requests in the repository.

What do I need to generate a pull request monitoring dashboard for my repository?

Generating a PR monitoring dashboard requires GitHub CLI access, repository PR metadata, and two helper scripts: pr-state.sh to compute per-PR state and merge-gate.sh to determine merge readiness.

How does automated code review state collection work for open pull requests?

Automated review state collection uses per-PR helper scripts to fetch reviews, inline comments, unresolved threads, check-runs, and bot-generated findings, classifying each pull request's readiness for merge.

Does the PR dashboard support triage for repositories with many open pull requests?

The dashboard processes up to 50 open pull requests simultaneously, listing titles, reviewer assignments, HEAD sha, last update time, and state to support triage and release planning.

Why are some pull requests marked as Rate-limited in the review dashboard?

Pull requests are marked Rate-limited when the merge-gate helper script detects rate-limit conditions that prevent full merge-readiness verification during the dashboard aggregation process.