state

Manage GitHub PR lifecycle states with labels and the GitHub CLI.

171|23|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/team-attention/hoyeon --skill state-team-attention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state
Source: https://github.com/team-attention/hoyeon/tree/main/skills/state
Command: npx skills add https://github.com/team-attention/hoyeon --skill state-team-attention

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes PR lifecycle state management within GitHub, enabling teams to queue, execute, pause, resume, and report on PRs from a single interface.

Core Features & Use Cases

  • Queue PRs for auto-execution with state:queued and optional auto-execute label
  • Begin execution, pause to blocked state, and resume to queued or executing
  • Monitor PR progress with status checks and list views across multiple PRs
  • Draft-based workflow transitions (created → queued → executing → ready)

Quick Start

Use commands like:

  • /state queue <PR#>
  • /state begin <PR#>
  • /state pause <PR#> "<reason>"
  • /state continue <PR#> [--run]
  • /state complete <PR#>
  • /state status [PR#]
  • /state list [--queued|--executing|--blocked|--all]

Frequently Asked Questions about state

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

FAQPage Schema
How do I manage GitHub PR lifecycle states from a single interface?

You can manage GitHub PR lifecycle states by applying labels like state:queued, state:executing, and state:blocked to queue, execute, pause, and resume pull requests. This centralizes PR state management through a unified interface using the GitHub CLI.

How do I automate PR execution queues in GitHub?

To automate PR execution queues in GitHub, you queue pull requests using the state:queued label and an optional auto-execute label. The system then transitions drafts through the created, queued, executing, and ready states automatically.

Can I pause a GitHub PR and resume it later?

Yes, you can pause a GitHub PR into a blocked state with a specific reason and resume it later. The workflow transitions the PR back to queued or executing states when you are ready to continue.

What is the best way to monitor progress across multiple GitHub PRs?

The best way to monitor progress across multiple GitHub PRs is by using status queries and list views. You can filter lists by queued, executing, blocked, or all states to track PR progress and check current statuses.

Do I need the GitHub CLI to enforce PR state transitions?

Yes, you need the GitHub CLI (gh) to enforce PR state transitions. The system reads guidelines from reference documents and uses the GitHub CLI to apply label changes and manage draft statuses.

Why use labels for PR state management instead of custom tracking tools?

Using labels for PR state management keeps all lifecycle data directly within GitHub natively. This avoids external tracking tools by enforcing state transitions via standard GitHub labels and draft statuses visible to all collaborators.