tobihagemann/turbo / claude/skills/pr
pr
VerifiedCreate or update the current branch's GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "open a PR", "update the PR", or "update PR description".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
| references/body-elements.md | markdown | 4.1 KB |
| references/create.md | markdown | 7.8 KB |
| references/update.md | markdown | 7.8 KB |
references/create.md
View on GitHub# Pull Request: Create
Draft a concise and descriptive title and a body for a PR. Explain the purpose of the changes, the problem they solve, and the general approach taken. When the changes involve clear runtime flows or state transitions, include Mermaid diagrams. When their point is structural, include a text sketch. When merging is hard to undo or reaches past the surface the PR edits, state the merge risk. When they add a user-facing surface or change how one looks, and this session already captured it, include screenshots.
## Phase 1: Analyze Changes
Take `<base>` as the base branch given with the request, or else the repository's default branch, and run `git fetch origin <base>`. Examine every commit message and the full diff against it (`git log origin/<base>..HEAD`, `git diff origin/<base>...HEAD`) to understand the overall changes. Analyze the diff for framing, diagram, and screenshot opportunities, and for merge risk.
Source every claim about prior behavior from the base branch itself, by reading its code with `git show origin/<base>:<path>`. A long session leaves the working tree carrying intermediate states that were never the state this PR is measured against, and describing one of those as the prior behavior misleads the reviewer.
Before writing that two pull requests must land together, check whether the consumer uses what changed: `git grep <symbol>` in its checkout, or the other repository's working copy when the dependency crosses repositories. When it does, name the actual cause. When it does not, drop the landing-order claim and keep any reference to the related pull request as plain context. State the claim as unverified when the consumer is not reachable.
When the PR closes an issue, read the issue before drafting.
## Phase 2: Run `/github-voice` Skill
Run the `/github-voice` skill to load writing style rules.
## Phase 3: Draft Title and Description
Pick a framing, then draft a title and description in it, embedding any diagrams, Merge Risk section, and screenshots in the body as [body-elements.md](body-elements.md) directs. Output the drafted title and description as chat text so the user can review it, followed by the path of each capture that will upload, if any. After that, name each added surface or changed look that none of those captures shows in its final state, if any, with the reason it goes unshown.
## Phase 4: Confirm and Create
Generate a random tag so the body file is unique across sessions:
```bash
head -c 4 /dev/urandom | xxd -p
```
Write the drafted body to `.turbo/pr/<tag>-body.md` (using the printed tag) with the Write tool.
Use `AskUserQuestion` to choose among three outcomes, and act on the one selected:
- **Post the PR now** — create it with the command below.
- **Edit the description first** — give the user the path to the body file, note the current branch, and stop there. Once they say they are done editing, check out that branch, then use `AskUserQuestion` again to offer posting the PR or cancelling, then act on that answer. Posting reads the file, so their edits carry through.
- **Cancel** — create no PR.
```bash
gh pr create --title "<TITLE>" --body-file .turbo/pr/<tag>-body.md
```
When the body references captures, add one `--attach <path>` per capture, using the absolute path the body references. Take the list from the body file as it stands when posting, re-reading it after the user edits it.
When the command reports a failed upload, act on what it printed, then report which captures the PR went up without:
- **No PR URL** — nothing uploaded and no PR exists. Remove the screenshot table and its heading from the body file and run the command again without `--attach`.
- **A PR URL** — the PR exists, and its body references the captures that did not upload by local path. Fetch the posted body with `gh pr view <PR_URL> --json body --jq .body`, remove each table column whose image is still a local path, write the result to the body file, and apply it with `gh pr edit <PR_URL> --body-file .turbo/pr/<tag>-body.md`.
When an uploaded capture was taken at a scale factor above 1, size it to its logical width as the Logical Width section of [body-elements.md](body-elements.md) directs: fetch the posted body with `gh pr view <PR_URL> --json body --jq .body`, replace each such capture's image, write the result to the body file, and apply it with `gh pr edit <PR_URL> --body-file .turbo/pr/<tag>-body.md`.
When the user asks, before the PR is posted, to change content this session committed for it, fold the change into the commit that carries that content instead of adding a commit, and push with `--force-with-lease` when that commit was already pushed. Update the drafted title and the body file where the change alters what they describe, then return to this gate.
When a base branch was given with the request, add `--base <base>`. Do not set `--assignee` unless the user explicitly asks to assign someone. Reserve `--draft` for an explicit request for a draft pull request on GitHub.
Then use the TaskList tool and proceed to any remaining task.
## Framing
Every body says what the change does and why. How it is organized past that follows from what the change is: pick the framing that carries the most user-visible meaning, and combine two when the change genuinely has both shapes.
### Summary Paragraph
The default. Use when the PR makes one coherent change with one purpose.
### Itemized Changes
Use when the PR carries several distinct changes and the reviewer needs the inventory. One item per change, ordered by what matters most.
### User Stories
Use when the change delivers capability someone can name. Write each as `As a <persona>, I want <capability> so that <outcome>.`
### Before and After
Use when the reviewer's question is what changed rather than what exists: several distinct fixes, or behavior that reads as a feature description unless the delta is spelled out. Give each item a Before line and an After line. Head each item with its user story in bold and list the Before and After lines beneath it. Reserve a plain heading, such as the name of the code the item touches, for an item that changes nothing a user or operator would notice.
Write Before lines in the past tense, with two exceptions. A sentence describing code the PR leaves alone stays present tense. A claim about what was merely possible stays modal ("could post"), never simple past, which asserts it happened.
### Rules
- Raise each item, heading included, to behavior a user or operator would notice. Mechanism the reviewer can read off the diff belongs in the diff. Leave out which existing pattern or sibling the implementation is modeled on.
- Describe the net change against the base. Leave out what the session tried and weighed along the way, and what the PR leaves undone: follow-ups, problems found but not fixed, and notes that code it leaves alone still behaves as before. When the PR closes an issue, still state any part of that issue it does not deliver.
- Write the body for someone who knows only the repository the PR targets. When the change is paired with work in another repository, name the interface the code calls and leave that repository's internal names, data shapes, and mechanisms out of the body. Explaining a cause does not license importing those internals. State the observable outcome instead. Describe the change on its own terms, without reference to how a different repository or product does it.
- When the PR closes an issue, open with `Closes #N`. Carry only what the issue does not already say: the interface being added, behavior a reviewer cannot infer from the diff, and above all any deviation from what the issue asked for. The issue carries the bug, its root cause, and the motivation; reference it rather than restating it.
- After cutting for any rule above, re-read what remains. A claim whose setup lived in a cut passage no longer stands on its own.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |