ship-pr
/ship-pr
Weryfikuje każdy PR w osobnym worktree, upraszcza diff i otwiera PR przez gh, gdy praca jest gotowa do recenzji.
- Autor
- Cynnamoroll ↗
- Repozytorium
- factory-stack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Weryfikuje każdy PR w osobnym worktree, upraszcza diff i otwiera PR przez gh, gdy praca jest gotowa do recenzji.
Oryginalny opis (EN)
Verify each PR in its own worktree with prove-it-works, run simplify on the diff, and open the PR with gh. Use when work is done and ready for review; not for a bare gh pr create when no isolated verify and simplify pass is needed, and not to watch an already-open PR (use watch-pr).
Jak działa
- 1. Shape the commits
- 2. Verify each PR independently
- 3. Clean the diff
- 4. Write the PR
- Done when
Podgląd SKILL.md
--- name: ship-pr description: "Verify each PR in its own worktree with prove-it-works, run simplify on the diff, and open the PR with gh. Use when work is done and ready for review; not for a bare gh pr create when no isolated verify and simplify pass is needed, and not to watch an already-open PR (use watch-pr)." license: MIT compatibility: droid disable-model-invocation: true --- # Ship PR Open PRs that a reviewer can trust: each one verified by a run that did not write the code, cleaned up, and described in one minute of reading. ## 1. Shape the commits Rebase into small, ordered commits. Each future PR lands on its own and the order tells the story: the failing test before the fix, the removal before the reshape. Prefer several narrow PRs to one large one. Stage only your files (`git add <files>`). A stack is a chain of base branches. The bottom PR targets the default branch, and each child targets its parent's branch. ## 2. Verify each PR independently For each PR branch, start a fresh run in its own worktree so the verdict does not come from the session that wrote the code: ```sh droid exec -m auto --auto medium --worktree "verify-<branch>" -o json \ "Check out <branch>. Run /prove-it-works on the change between <base> and <branch>. End with PASS, PASS+NOTES, or FAIL and the evidence." ``` Run several at once with `&` and `wait`. Green CI and a bot approval are not verdicts, because neither runs the change the way a user would. A FAIL goes back to the author step. Do not open that PR. Record the verdict's commit. Before trusting a verdict after a rebase, compare `git diff <base>...<verdict-sha> | git patch-id --stable` with the same for the current head. Different patch IDs mean a fresh verification. If `droid exec` fails on authentication, ask the user to export `FACTORY_API_KEY` in their shell. Never write a key to a file. ## 3. Clean the diff Run Droid's built-in `simplify` skill on each PR's diff and apply the fixes that hold up. Remove comments that narrate steps. Rerun `prove-it-works` if `simplify` changed behavior-bearing code. ## 4. Write the PR - **Title.** Conventional Commits, `type(scope): subject`, imperative, no trailing period, naming a real symbol when one carries the change. - **Body.** Run `tighten-prose` on it. Use `##` headings in this order and drop any with nothing to say: - `## Why`: the problem and approach in 1 to 3 sentences. - `## What changed`: 1 to 3 bullets. - `## Scope`: what it covers and what it leaves out. - `## Tradeoffs`: only rejected alternatives a reviewer would ask about. - `## Blast radius`: who or what it touches and why that is safe or risky. - `## Verification`: the verdict and 1 to 3 run paths with outcomes. Perf gets one number, before and after. Write the body to a file. Open the PR ready, not draft: ```sh gh pr create --base <base> --head <branch> --title "<title>" --body-file /tmp/pr-body.md ``` Then read it back with `gh pr view <number>`. ## Done when Every PR opened has a PASS or PASS+NOTES verdict whose patch ID matches its head, `simplify` ran on its diff, and the reply lists each PR as a full `https://github.com/<owner>/<repo>/pull/<number>` URL with its verdict. Opening a PR does not start a watch. The user runs `/watch-pr` when the stack is complete. Remove the `verify-*` worktrees when done.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Cynnamoroll/factory-stack | 100 | MIT |
| tester-army/e2e | 100 | Apache-2.0 |
| e2e-inc/e2e | 100 | Apache-2.0 |
| seancabalse/agentic-playbook | 100 | MIT |
| shreypaharia/octomux | 90 | MIT |
| devcules/devcules | 86 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki a801906dadc9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90go
Szybko wysyła małe zmiany w Go: weryfikuje, upraszcza kod i otwiera pull request, gdy zmiana jest mała i czysta. - 100ship
Przegląda diff lokalnie, otwiera PR, pilnuje recenzji AI i CI, a potem scala zmianę do domyślnej gałęzi. - 100pr-watch-fix-renovate
Równolegle obsługuje wszystkie otwarte PR-y od Renovate, każdy w osobnym worktree, by zatwierdzić albo sklasyfikować aktualizacje zależności. - 100pr-create
Przeprowadza przez zatwierdzenie zmian, wypchnięcie gałęzi i utworzenie pull requesta, gdy praca jest gotowa do przeglądu. - 100ship
Sprawdza, czy praca jest naprawdę skończona, potem zapisuje zmiany w commicie, otwiera PR, kończy gałąź i wdraża zmianę. - 100pr
Otwiera pull request z dobrze napisanym opisem, gdy praca na gałęzi jest skończona i gotowa do przeglądu.