publish

Converts draft GitHub pull requests to Ready for Review state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the transition of Draft PRs to the Ready for Review state, reducing manual tracking and speeding up the code review process.

Core Features & Use Cases

  • PR readiness automation: Detects Draft PRs and performs the state transition to Ready for Review.
  • State-validation: Verifies current PR status and enforces prerequisites before publishing.
  • Audit-friendly: records publishing actions and statuses for traceability.

Quick Start

Use the publish Skill to convert a current Draft PR into Ready for Review.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I convert a Draft PR to Ready for Review automatically?

To convert a Draft PR to Ready for Review automatically, you can use the publish Skill within your GitHub PR workflows to detect draft states and transition them without manual intervention.

What is GitHub PR readiness automation?

GitHub PR readiness automation detects Draft PRs and performs the state transition to Ready for Review, enforcing state prerequisites and recording publish events for audit traceability.

Does the publish Skill verify PR status before changing to Ready for Review?

Yes, the publish Skill verifies the current PR status and enforces state prerequisites before publishing, ensuring invalid PRs remain in Draft state until requirements are met.

Are GitHub PR publish actions recorded for audit purposes?

GitHub PR publish actions are recorded by the Skill using internal routines, capturing publishing actions and statuses to provide a traceable audit log of readiness transitions.

Can I use this to reduce manual tracking in GitHub PR workflows?

You can use this Skill to reduce manual tracking in GitHub PR workflows by automating readiness transitions, updating labels, and recording publish events without manual intervention.

What are the limitations of automating Draft PR transitions?

Automating Draft PR transitions requires enforcing state prerequisites via internal routines, meaning the Skill will only publish PRs that meet current status validation rules within the GitHub workflow.