Automated summary
Converts a GitHub pull request from Draft to Ready for review after validating its state in a label-based workflow.
Strengths
- Auto-detects the PR for the current branch or accepts a number/URL
- Validates state before acting and blocks invalid transitions
- Clear error messages that name the next command to run
- Delegates the transition to /state complete for consistent state tracking
Limitations
- Tightly coupled to the external /state and /execute commands and their label conventions
- GitHub-specific and assumes a Draft PR workflow
- Does not handle other review prep such as assigning reviewers or resolving conflicts
Use this skill when a working PR is ready to move from Draft to Ready for review inside a /state workflow.
Security analysis
SafeThe skill only describes changing a draft pull request to ready-for-review using GitHub state labels and related workflows. It does not include destructive commands, credential exfiltration, obfuscated payloads, or safety-disabling instructions. Bash usage is implied for PR operations but is appropriate and bounded.
No concerns found
How this analysis is madeExamples
/publish/publish 123/publish https://github.com/owner/repo/pull/123name: publish description: | "/publish", "publish PR", "PR ready", "publish PR", "remove Draft" Convert Draft PR to Ready for review allowed-tools:
- Bash
- Read
- Glob
dev.publish - PR Ready Processing
Purpose
Convert Draft PR to Ready state for review.
Input
| Input | Action |
|-------|------|
| /publish | Auto-detect PR from current branch |
| /publish 123 | Publish PR #123 |
| /publish <PR URL> | Extract PR# from URL |
Execution Conditions
- PR must be in
state:executingstate - If
state:blocked→ Run/state continuefirst - Error if already Ready
State verification: Check with /state status
Workflow
STEP 1: Check PR Info
- Parse argument (find PR from current branch if none)
- Check current state with
/state status <PR#>
STEP 2: Validate State
| Condition | Result |
|------|------|
| state:executing | ✅ Proceed |
| state:blocked | ❌ "Run '/state continue' first" |
| No label (created) | ❌ "Not executed yet" |
| isDraft = false | ❌ "Already published" |
STEP 3: Execute Publish
Call /state complete <PR#>:
- Remove
state:executinglabel - Convert Draft → Ready
- Record "Published" comment
STEP 4: Output Result
Success:
✅ PR #123 published successfully
URL: https://github.com/owner/repo/pull/123
Status: Ready for review
Error Handling
| Error | Message | |-------|--------| | No PR | "No PR found for current branch" | | Created state | "Run '/execute {PR#}' first" | | Blocked state | "Run '/state continue {PR#}' first" | | Already ready | "Already published (not a draft)" |
State Transition
executing → ready (via /state complete)
Note: From blocked, first transition to executing with /state continue
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/publish-pull-request-mma3jrce/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/publish-pull-request-mma3jrce' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/publish-pull-request-mma3jrce/download' --output '.skill-downloads/publish-pull-request-mma3jrce/SKILL.md.part' && mv '.skill-downloads/publish-pull-request-mma3jrce/SKILL.md.part' '.skill-downloads/publish-pull-request-mma3jrce/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/publish-pull-request-mma3jrce/SKILL.md' && test -s '.skill-downloads/publish-pull-request-mma3jrce/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/publish' && cp -R '.skill-downloads/publish-pull-request-mma3jrce' '.claude/skills/publish'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/publish-pull-request-mma3jrce'openskills read 'publish-pull-request-mma3jrce'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/publish-pull-request-mma3jrce/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.