JetBrains/thinkrail / packages/pi-thinkrail-workflow/skills/shipping-a-pr
shipping-a-pr
VerifiedUse when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.2 KB |
| body.md | markdown | 1.3 KB |
| checks.md | markdown | 3.9 KB |
| creating.md | markdown | 4.7 KB |
| review-comments.md | markdown | 1.7 KB |
| screenshots.md | markdown | 2.8 KB |
| syncing.md | markdown | 1.6 KB |
body.md
View on GitHub# body.md — maintain PR title or body
Entry: an open PR plus a requested title/body change. Saves `.thinkrail/context/pr-body.md` when
editing the body (kept as an artifact; the next edit overwrites it). Default completion is snapshot mode; preserve wait mode only when selected by the
spine's explicit remote-completion rule.
1. Fetch the current title and body (`gh pr view <n> --json title,body`) and read the repository's
`.github/PULL_REQUEST_TEMPLATE.md` when present. Preserve existing sections, issue links, checklist
items, and unrelated content; apply only the requested mutation.
2. For a body edit, write the complete candidate to `.thinkrail/context/pr-body.md`. Immediately before
`gh pr edit`, fetch the current body again; if it changed, merge the requested mutation into that
fresh body instead of overwriting concurrent edits. Use `gh pr edit <n> --body-file ...`, never an
inline body. For a title edit, immediately re-fetch the current title too; if it changed, reapply
only the requested mutation to that fresh title before `gh pr edit <n> --title ...`.
3. Fetch the resulting title/body once to verify the requested mutation landed. Leave the body file
in place.
## Next
Read and follow `checks.md` in the selected completion mode.
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 |