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.
Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions.
Install Write Clear Pull Request
$ npx skills add satoshikawato/gbdraw --skill write-clear-pull-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install satoshikawato/gbdraw write-clear-pull-request --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/satoshikawato/gbdraw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .claude/skills/write-clear-pull-request && 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 "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .claude/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-requestType 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 satoshikawato/gbdraw --skill write-clear-pull-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install satoshikawato/gbdraw write-clear-pull-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/satoshikawato/gbdraw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .agents/skills/write-clear-pull-request && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .agents/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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 satoshikawato/gbdraw --skill write-clear-pull-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install satoshikawato/gbdraw write-clear-pull-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/satoshikawato/gbdraw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .cursor/skills/write-clear-pull-request && 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 "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .cursor/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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/satoshikawato/gbdraw.git --path .agents/skills/write-clear-pull-request--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 satoshikawato/gbdraw --skill write-clear-pull-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install satoshikawato/gbdraw write-clear-pull-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/satoshikawato/gbdraw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .gemini/skills/write-clear-pull-request && 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 "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .gemini/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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 satoshikawato/gbdraw write-clear-pull-requestInstalls 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 satoshikawato/gbdraw --skill write-clear-pull-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/satoshikawato/gbdraw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .github/skills/write-clear-pull-request && 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 "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .github/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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 satoshikawato/gbdraw --skill write-clear-pull-request -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install satoshikawato/gbdraw write-clear-pull-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/satoshikawato/gbdraw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-clear-pull-request .opencode/skills/write-clear-pull-request && 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 "write-clear-pull-request" agent skill from https://github.com/satoshikawato/gbdraw/tree/main/.agents/skills/write-clear-pull-request into .opencode/skills/write-clear-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-clear-pull-request", 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
write-clear-pull-request- GitHub stars
- 154
- Token cost
- ~539 tokens
- SKILL.md length
- 209 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions.
- Works in 6 steps: Name the concrete action and object. → State the reason when it is not obvious. → State the behavior or review condition… → …
- Changing a PR title
- SKILL.md covers Audience, Opening, Workflow and Regression example
- Calls gh and node
What it does
Write Clear Pull Request is an agent skill from satoshikawato/gbdraw. Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions. Use whenever creating or changing a PR title or body, or reviewing either for clarity.
Its SKILL.md is about 540 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 and Bioinformatics. The repository describes itself as: A genome diagram generator for microbes and organelles. The licence is MIT.
When your agent uses it
- Changing a PR title
- Reviewing either for clarity
Example prompts
- “/write-clear-pull-request”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Name the concrete action and object.
- State the reason when it is not obvious.
- State the behavior or review condition after merge.
- Replace unexplained local abstractions in the title and summary.
- Check that the text makes sense without prior plans or PR history.
- Save the complete body, then run
What it can do on your machine
Read from SKILL.md and the folder at commit fe6861f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Write Clear Pull Request loads about 539 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 209 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 passed
The automated check found no risky patterns in SKILL.md.
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 satoshikawato/gbdraw at commit fe6861f, republished under its MIT licence (© satoshikawato). 209 words, ~539 tokens.
Download SKILL.mdSave it as
.claude/skills/write-clear-pull-request/SKILL.md (or your agent's skills folder).- name
- write-clear-pull-request
- description
- Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions. Use whenever creating or changing a PR title or body, or reviewing either for clarity.
Write clear pull requests
Audience
Assume the reader knows gbdraw, Git, and GitHub, but has not read an implementation plan, earlier PRs, or private discussion.
Opening
- Write the title as a concrete action plus a concrete object.
- Begin the body directly with a concise paragraph that says what changes, why, and what differs after merge. Do not add a heading above this paragraph.
- Treat internal classifications and process labels as metadata, not as the primary explanation.
- Preserve exact check names, paths, branch names, options, and code identifiers in backticks. Explain their role in ordinary language when the name is not self-explanatory.
Policy terms may appear in later technical or evidence sections. They fail this standard only when they replace the concrete explanation in the title or opening paragraph.
Workflow
Name the concrete action and object.
State the reason when it is not obvious.
State the behavior or review condition after merge.
Replace unexplained local abstractions in the title and summary.
Check that the text makes sense without prior plans or PR history.
Save the complete body, then run:
bash node tools/check-pr-language.mjs --title "<concrete title>" --body-file <body.md>
Run gh pr create or a wording-changing gh pr edit separately after the checker passes.
Regression example
Bad title:
Promote steady-state CI topology and finalize main admissionBad opening:
This promotion removes the transition-only CI topology from main and completes the admission-policy cutover.Clear title:
Stop rerunning full CI on dev-to-main pull requestsClear opening:
This PR removes CI jobs that were needed only while the new main-merge check was being introduced. After the branch-protection update, dev-to-main pull requests will require only `Promotion / gate` and `CodeQL`.© satoshikawato, MIT. 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 .agents/skills/write-clear-pull-request of satoshikawato/gbdraw.
Open the folder on GitHubat commit fe6861f
Compare with similar skills
Write Clear Pull Request 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 |
|---|---|---|---|---|---|---|
| Write Clear Pull Request this skillsatoshikawato/gbdraw | 154 | — | ~539 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 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 | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
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.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
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.
More from satoshikawato/gbdraw
Web Gallery Screenshot Maintenance
satoshikawato/gbdraw
Maintain gbdraw Web Gallery tutorial screenshots, manual text, and structured tutorial content.
Related
Categories
Questions about Write Clear Pull Request
What does Write Clear Pull Request do?
Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions. Write Clear Pull Request is an agent skill from satoshikawato/gbdraw. Write, edit, or review gbdraw pull request titles and maintainer-facing descriptions.
When should I use Write Clear Pull Request?
Write Clear Pull Request fits situations like: changing a PR title; reviewing either for clarity.
How do I install Write Clear Pull Request in Claude Code?
Run `npx skills add satoshikawato/gbdraw --skill write-clear-pull-request -a claude-code`. Or copy the skill folder (.agents/skills/write-clear-pull-request in satoshikawato/gbdraw) into .claude/skills/write-clear-pull-request in your project. Claude Code loads it when a task matches its description.
How do I install Write Clear Pull Request in Codex?
Run `npx skills add satoshikawato/gbdraw --skill write-clear-pull-request -a codex`. Or copy the skill folder (.agents/skills/write-clear-pull-request in satoshikawato/gbdraw) into .agents/skills/write-clear-pull-request in your project. Codex loads it when a task matches its description.
Can I use Write Clear Pull Request 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 satoshikawato/gbdraw --skill write-clear-pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-clear-pull-request, .gemini/skills/write-clear-pull-request, .github/skills/write-clear-pull-request and .opencode/skills/write-clear-pull-request in your project.
What does Write Clear Pull Request need to run?
Going by SKILL.md and its folder, Write Clear Pull Request needs the command-line tools its instructions call (gh and node).
Does Write Clear Pull Request access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Write Clear Pull Request safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write Clear Pull Request use?
Write Clear Pull Request is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Clear Pull Request use?
About 539 tokens (SKILL.md is roughly 2.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 Write Clear Pull Request?
Skills that share tags, products or a category with Write Clear Pull Request: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Clear Pull Request?
satoshikawato (a GitHub user) maintains it in satoshikawato/gbdraw, which has 154 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: satoshikawato/gbdraw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.