prauto-check-status

Name: prauto-check-status
Availability: InStock
Author: selhorys

Aggregate GitHub issue and PR labels to determine the next prauto heartbeat action.

15|Updated Feb 8, 2026

Search Tags:#automation #github #review #status #heartbeat #prauto

Ready to run

npx skills add https://github.com/selhorys/dataspoke-baseline --skill prauto-check-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prauto-check-status
Source: https://github.com/selhorys/dataspoke-baseline/tree/main/.claude/skills/prauto-check-status
Command: npx skills add https://github.com/selhorys/dataspoke-baseline --skill prauto-check-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automatically determine the next action in prauto-driven workflows by aggregating GitHub issue and PR status and heartbeat traces.

Core Features & Use Cases

Aggregates labels (prauto:ready, prauto:wip, prauto:plan-review, prauto:done, prauto:failed) and reviewer approvals to surface current state.
Predicts the next heartbeat action (analysis, implementation, PR-review, or squash-finalize) based on priority rules and quota/lock states.
Detects quota pauses via the prauto:quota-paused marker and latest comments to avoid wasted work.
Use Case: A team runs prauto-check-status to decide whether to start work on a ready issue or finalize a PR.

Quick Start

Run prauto-check-status on the target repository to display the recommended next heartbeat action.

Frequently Asked Questions about prauto-check-status

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

FAQPage Schema

How do I predict the next prauto heartbeat action for GitHub PRs?▼

To predict the next prauto heartbeat action, aggregate GitHub issue and PR labels alongside reviewer approvals. The system enforces quota, lock state, and paused marker checks to output a precise action like analysis, implementation, or PR-review.

How does prauto status aggregation handle quota pauses and lock states?▼

Prauto status aggregation detects quota pauses via the prauto:quota-paused marker and validates the latest lock state. This mechanism avoids wasted work by ensuring the heartbeat only triggers when resources are available and issues are unresolved.

What GitHub labels are required to determine the next automated PR review action?▼

Determining the next automated PR review action requires ready, wip, review, done, and failed labels. These labels surface the current state to apply priority rules for the next heartbeat step.

Can I use prauto-check-status to decide whether to start work or finalize a pull request?▼

Yes, you can use prauto-check-status to decide whether to start work or finalize a pull request. It aggregates issue and PR status to recommend whether the heartbeat should begin implementation or execute a squash-finalize.

Why does my prauto workflow skip ready issues and fail to trigger the next heartbeat?▼

Your prauto workflow may skip ready issues if a quota-paused marker is detected or the repository is in a locked state. The system checks these constraints to prevent triggering unnecessary heartbeat actions.

What is the best way to automate GitHub PR status checks for continuous integration workflows?▼

The best way to automate GitHub PR status checks is to run prauto-check-status on the target repository. It aggregates labels and reviewer approvals to display the recommended next heartbeat action for continuous integration.