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 |
screenshots.md
View on GitHub# screenshots.md — before/after evidence for reviewers
Entry: a PR exists (or was just created) for a UI-visible change. Saves PNGs under
`.thinkrail/context/pr-shots/` and rewrites the PR body to reference them. Preserve wait mode only
when the caller explicitly requested remote completion; otherwise use snapshot mode, including after
PR creation.
## Capture
- **After** = the scenario on the branch build; **Before** = the *same* scenario at the base branch
(check out detached, rebuild, capture, return). Same viewport, same scenario — the pair must diff
visually.
- Capture with whatever drives the app in this project: the e2e harness with a throwaway capture
spec, or a browser-automation session against a running dev host. A capture spec is a throwaway —
it never ships, and *this* doc owns its cleanup (Next below): creating.md's clean-branch gate has
already run on every entry path here and will not catch it.
- Stage the picked shots as `.thinkrail/context/pr-shots/<name>.png` with names a reviewer reads
(`loader-before-gap.png`, `loader-after-working.png`).
## Attach — review-only assets ref (the default)
Screenshots never enter the PR's file tree. Push them as an orphan ref and reference SHA-pinned
URLs:
```bash
TREE_INPUT=""
for f in .thinkrail/context/pr-shots/*.png; do
sha=$(git hash-object -w "$f")
TREE_INPUT+=$(printf '100644 blob %s\t%s' "$sha" "$(basename "$f")")$'\n'
done
TREE=$(printf '%s' "$TREE_INPUT" | git mktree)
COMMIT=$(printf 'PR screenshots (review-only ref)\n' | git commit-tree "$TREE")
git push -f origin "$COMMIT:refs/heads/assets/<topic>"
```
Then update the body — **never rebuild it**: fetch the current one first
(`gh pr view <n> --json body -q .body > .thinkrail/context/pr-body.md`), add or update a
`## Screenshots` section in it referencing each image as
`https://github.com/<owner>/<repo>/blob/<COMMIT>/<name>.png?raw=true` (pinned to the pushed commit
SHA so later branch pushes never break the images), then
`gh pr edit <n> --body-file .thinkrail/context/pr-body.md`. A body built from
scratch here would erase the PR's summary, testing notes, and issue links.
Fallback (the user sometimes prefers it): leave the PNGs staged and hand over their paths — the
user drags them into GitHub by hand. Offer the choice only when the user has signaled it; the
assets ref is the default.
## Next
Clean up this phase's capture scaffolds (specs, throwaway builds) once the body edit lands. The
staged shots in `.thinkrail/context/pr-shots/` and the body file stay: they are the user's artifacts,
never deleted by a workflow. If any scaffolding was committed, the commit that removes it
is pushed too — a deletion left in the working tree ships nothing. That push does not change the
completion mode. Read and follow `checks.md` in the selected 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 |