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 a pull-request title and body from the current branch against its base.
Install PR Description
$ npx skills add teddytennant/wizard --skill pr-description -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install teddytennant/wizard pr-description --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/teddytennant/wizard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .claude/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .claude/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-descriptionType 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 teddytennant/wizard --skill pr-description -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install teddytennant/wizard pr-description --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .agents/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .agents/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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 teddytennant/wizard --skill pr-description -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install teddytennant/wizard pr-description --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .cursor/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .cursor/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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/teddytennant/wizard.git --path registry/skills/teddytennant/pr-description--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 teddytennant/wizard --skill pr-description -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install teddytennant/wizard pr-description --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .gemini/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .gemini/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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 teddytennant/wizard pr-descriptionInstalls 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 teddytennant/wizard --skill pr-description -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .github/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .github/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .github/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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 teddytennant/wizard --skill pr-description -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install teddytennant/wizard pr-description --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/teddytennant/wizard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/registry/skills/teddytennant/pr-description .opencode/skills/pr-description && 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-description" agent skill from https://github.com/teddytennant/wizard/tree/main/registry/skills/teddytennant/pr-description into .opencode/skills/pr-description/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-description", 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-description- GitHub stars
- 53
- Token cost
- ~484 tokens
- SKILL.md length
- 253 words
- Files
- 2
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Write a pull-request title and body from the current branch against its base.
- Works in 3 steps: git_status. Note the branch, the likely… → The commits and the diff against that… → A PR template if the repo ships one…
- Tasks that involve Pull requests
- SKILL.md covers What to look at, Title, Body and How to verify
- Calls git
What it does
PR Description is an agent skill from teddytennant/wizard. Write a pull-request title and body from the current branch against its base. Why, what, how to test. No marketing.
Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in Development, covering Pull requests. It works with Git. The repository describes itself as: The fastest agent in your terminal. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
Example prompts
- “/pr-description”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- git_status. Note the branch, the likely base (main or master, or whatever this repo uses), and whether anything is still uncommitted.
- The commits and the diff against that base (git log ..HEAD, git_diff or git diff ...HEAD). Read both. Describe only what is in them.
- A PR template if the repo ships one (.github/pull_request_template.md and the usual variants). Use its headings. Do not invent a template…
What it can do on your machine
Read from SKILL.md and the folder at commit b4290bf. 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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 Description loads about 484 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 253 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 teddytennant/wizard at commit b4290bf, republished under its Apache-2.0 licence (© teddytennant). 253 words, ~484 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-description/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- pr-description
- description
- Write a pull-request title and body from the current branch against its base. Why, what, how to test. No marketing.
Pull request description
Write the title and body. Do not open, push, or edit the PR unless the user asked.
What to look at
git_status. Note the branch, the likely base (mainormaster, or whatever this repo uses), and whether anything is still uncommitted.- The commits and the diff against that base (
git log <base>..HEAD,git_difforgit diff <base>...HEAD). Read both. Describe only what is in them. - A PR template if the repo ships one (
.github/pull_request_template.mdand the usual variants). Use its headings. Do not invent a template the tree does not have.
If there are no commits against the base, say so and stop.
Title
One line, imperative, specific. The first conventional-commit subject on the branch is a starting point, not a requirement. Skip [WIP] unless the user said the PR is unfinished.
Body
Match the repo's voice. When there is no template, use this shape:
## Why
<the problem this branch closes. one or two sentences. not a feature list.>
## What
<what the diff does, in the order a reviewer will read it. name files and
behaviour, not effort.>
## Test plan
- [ ] <a command a reviewer can run>
- [ ] <the case that used to fail>Rules:
- Every claim is grounded in the diff or the log. "Improves performance" needs a measurement or it comes out.
- Do not list files the diff does not touch.
- Do not thank reviewers, do not add emoji, do not write a sales paragraph.
- A revert or a mechanical version bump is one sentence, not an essay.
How to verify
Name the commands a reviewer can run. Not "tested locally". Leave template boxes unchecked unless those commands were actually run.
If the diff includes a secret, say that a secret is present and stop; do not put it in the PR body.
© teddytennant, 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
SKILL.md and 1 other file in registry/skills/teddytennant/pr-description of teddytennant/wizard.
- SKILL.md
- manifest.toml
Open the folder on GitHubat commit b4290bf
Compare with similar skills
PR Description 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 Description this skillteddytennant/wizard | 53 | — | ~484 | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Open Code Review CLIalibaba/open-code-review | 46k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
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.
More from teddytennant/wizard
Plain Writing
teddytennant/wizard
Write prose that reads like a person wrote it, not a model. An agent skill from teddytennant/wizard.
Conventional Commit
teddytennant/wizard
Write a conventional commit subject and body from the current diff.
Evolve
teddytennant/wizard
How to extend Wizard via /evolve. An agent skill from teddytennant/wizard.
Undercover
teddytennant/wizard
Keep git history clean in public repos. An agent skill from teddytennant/wizard.
Coding
teddytennant/wizard
Baseline coding workflow. An agent skill from teddytennant/wizard.
Related
Works with
Categories
Questions about PR Description
What does PR Description do?
Write a pull-request title and body from the current branch against its base. PR Description is an agent skill from teddytennant/wizard. Write a pull-request title and body from the current branch against its base.
When should I use PR Description?
PR Description fits situations like: tasks that involve Pull requests.
How do I install PR Description in Claude Code?
Run `npx skills add teddytennant/wizard --skill pr-description -a claude-code`. Or copy the skill folder (registry/skills/teddytennant/pr-description in teddytennant/wizard) into .claude/skills/pr-description in your project. Claude Code loads it when a task matches its description.
How do I install PR Description in Codex?
Run `npx skills add teddytennant/wizard --skill pr-description -a codex`. Or copy the skill folder (registry/skills/teddytennant/pr-description in teddytennant/wizard) into .agents/skills/pr-description in your project. Codex loads it when a task matches its description.
Can I use PR Description 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 teddytennant/wizard --skill pr-description -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-description, .gemini/skills/pr-description, .github/skills/pr-description and .opencode/skills/pr-description in your project.
What does PR Description need to run?
Going by SKILL.md and its folder, PR Description needs the command-line tools its instructions call (git).
Does PR Description access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Description 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 PR Description use?
PR Description 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 Description use?
About 484 tokens (SKILL.md is roughly 1.9k 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 Description?
Skills that share tags, products or a category with PR Description: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Description?
teddytennant (a GitHub user) maintains it in teddytennant/wizard, which has 53 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: teddytennant/wizard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.