Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Create pull requests for esphome/device-builder. An agent skill from esphome/device-builder.
Install PR Workflow
$ npx skills add esphome/device-builder --skill pr-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install esphome/device-builder pr-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-workflow .claude/skills/pr-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .claude/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add esphome/device-builder --skill pr-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install esphome/device-builder pr-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pr-workflow .agents/skills/pr-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .agents/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add esphome/device-builder --skill pr-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install esphome/device-builder pr-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pr-workflow .cursor/skills/pr-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .cursor/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/esphome/device-builder.git --path .claude/skills/pr-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add esphome/device-builder --skill pr-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install esphome/device-builder pr-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pr-workflow .gemini/skills/pr-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .gemini/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install esphome/device-builder pr-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add esphome/device-builder --skill pr-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pr-workflow .github/skills/pr-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .github/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add esphome/device-builder --skill pr-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install esphome/device-builder pr-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esphome/device-builder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pr-workflow .opencode/skills/pr-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-workflow" agent skill from https://github.com/esphome/device-builder/tree/main/.claude/skills/pr-workflow into .opencode/skills/pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-workflow- GitHub stars
- 122
- Token cost
- ~1k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create pull requests for esphome/device-builder. An agent skill from esphome/device-builder.
- Works in 7 steps: Create branch from origin/main → Read the PR template → Tick exactly one "Types of changes" box → …
- Submitting changes
- SKILL.md covers 1. Create branch from…, 2. Read the PR template, 3. Tick exactly one "Types of… and 4. Frontend coordination, plus 3 more sections
- Calls git and gh
What it does
PR Workflow is an agent skill from esphome/device-builder. Create pull requests for esphome/device-builder. Use when creating PRs, submitting changes, or preparing contributions.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: ESPHome Device Builder Dashboard. The licence is Apache-2.0.
When your agent uses it
- Submitting changes
- Preparing contributions
Example prompts
- “/pr-workflow”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 096b0e6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Workflow loads about 1k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 495 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from esphome/device-builder at commit 096b0e6, republished under its Apache-2.0 licence (© esphome). 495 words, ~1,041 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-workflow/SKILL.md (or your agent's skills folder).- name
- pr-workflow
- description
- Create pull requests for esphome/device-builder. Use when creating PRs, submitting changes, or preparing contributions.
- allowed-tools
- Read, Bash, Glob, Grep
device-builder PR Workflow
When creating a pull request for esphome/device-builder, follow
these steps. The repo's conventions are documented in
CLAUDE.md; this skill summarises the parts
that matter at PR-creation time.
1. Create branch from origin/main
There is no fork in this workflow — origin already points at
esphome/device-builder. Always re-fetch first so the branch is
based on the latest main:
git fetch origin
git checkout -b <branch-name> origin/main2. Read the PR template
Before creating a PR, read .github/PULL_REQUEST_TEMPLATE.md to
understand the required sections. Fill in every section — do
not skip or abbreviate.
3. Tick exactly one "Types of changes" box
.github/workflows/pr-labels.yaml parses the PR description for a
- [x] ... \<label>`` line and applies the canonical label
automatically. The job fails if zero boxes are ticked or if
more than one is ticked — always tick exactly one. Pick whichever
fits best from:
breaking-change, new-feature, enhancement, bugfix,
refactor, docs, maintenance, ci, dependencies.
The label is what release-drafter uses to slot the PR into the right release-notes section, so the choice is editorial — pick the one a future release-notes reader would expect.
4. Frontend coordination
The frontend (esphome/device-builder-frontend) ships prebuilt
inside our wheel. If the PR touches anything the frontend consumes
— new ConfigEntryType values, new WS commands or events, model
shape changes — flag it under Frontend coordination and link
the companion PR there.
5. Commit message conventions
- Imperative-mood subject line — "Add X", not "Added X".
- No
Co-Authored-By: Claudetrailer. Project preference. - One logical change per commit; let pre-commit run (ruff, codespell, yaml/json/python checks). If a hook auto-fixes something, re-stage and re-commit.
Show full SKILL.md (246 more words)Show less
6. Push and create the PR
Always read .github/PULL_REQUEST_TEMPLATE.md from the repo at
PR-creation time and use it verbatim as the body — do not
reproduce, paraphrase, or trim the template anywhere else, or it
will silently drift out of sync as the template evolves.
When filling in the template:
- Replace the
<!-- ... -->prompt comments with the actual prose for that section. Do not delete anything else. - Leave all the checkboxes in place. Do not remove rows you aren't ticking — release-drafter / the auto-labeller and the human reviewer both rely on the full list being present.
- Tick exactly one "Types of changes" box (see step 3). For the
Frontend coordination and Checklist sections, only tick boxes
you have actually verified; leave the rest as
- [ ]. - Do not escape characters from the template. Backticks,
asterisks, angle brackets, etc. must be passed through verbatim
— escaping a backtick to
\`breaks the auto-labeller's regex (which looks for`<label>`) and corrupts inline code in the rendered PR. The template is already valid Markdown; do not rewrite it for shell quoting. Use--body-file, never--body "..."with shell-escaping.
git push -u origin <branch-name>
# Read .github/PULL_REQUEST_TEMPLATE.md, fill it in as above,
# write the result to a temp file, then:
gh pr create --repo esphome/device-builder --base main \
--title "Imperative subject under 70 chars" \
--body-file /tmp/pr-body.mdThe keep-the-checklist-honest rule applies — only tick a checklist
box you've actually verified. An untouched components.json is
verified by running git diff --stat origin/main..HEAD -- \ esphome_device_builder/definitions/components.json; doc updates
are verified by inspecting the diff.
7. After the PR is open
CI runs lint, the test matrix (incl. Windows), and the label
applier. If pr-labels fails, the description checkbox is missing
or unrecognised — edit the PR body, don't push an empty commit.
© esphome, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/pr-workflow of esphome/device-builder.
Open the folder on GitHubat commit 096b0e6
Compare with similar skills
PR Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Workflow this skillesphome/device-builder | 122 | — | ~1k | Automated safety check: Notes | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
Related
Categories
Questions about PR Workflow
What does PR Workflow do?
Create pull requests for esphome/device-builder. An agent skill from esphome/device-builder. PR Workflow is an agent skill from esphome/device-builder. Create pull requests for esphome/device-builder.
When should I use PR Workflow?
PR Workflow fits situations like: submitting changes; preparing contributions.
How do I install PR Workflow in Claude Code?
Run `npx skills add esphome/device-builder --skill pr-workflow -a claude-code`. Or copy the skill folder (.claude/skills/pr-workflow in esphome/device-builder) into .claude/skills/pr-workflow in your project. Claude Code loads it when a task matches its description.
How do I install PR Workflow in Codex?
Run `npx skills add esphome/device-builder --skill pr-workflow -a codex`. Or copy the skill folder (.claude/skills/pr-workflow in esphome/device-builder) into .agents/skills/pr-workflow in your project. Codex loads it when a task matches its description.
Can I use PR Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add esphome/device-builder --skill pr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-workflow, .gemini/skills/pr-workflow, .github/skills/pr-workflow and .opencode/skills/pr-workflow in your project.
What does PR Workflow need to run?
Going by SKILL.md and its folder, PR Workflow needs the command-line tools its instructions call (git and gh). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep.
Does PR Workflow access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Workflow safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does PR Workflow use?
PR Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Workflow use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to PR Workflow?
Skills that share tags, products or a category with PR Workflow: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Workflow?
esphome (a GitHub organization) maintains it in esphome/device-builder, which has 122 GitHub stars. The repository was last updated on October 10, 2026.
Source: esphome/device-builder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.