Programowanie · Automatyzacja
park
/park
Odkłada funkcję na jej gałęzi bez scalania do main, gdy praca jest skończona, ale nie jest jeszcze gotowa do wydania.
Dla kogo
- Autor
- slavochek2 ↗
- Repozytorium
- claritypledge ↗
- Licencja
- AGPL-3.0
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
Licencja
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
Co robi i kiedy
Odkłada funkcję na jej gałęzi bez scalania do main, gdy praca jest skończona, ale nie jest jeszcze gotowa do wydania.
Oryginalny opis (EN)
Park a feature on its branch without merging to main. Use when work is done but you're not ready to ship yet.
Jak działa
- Pipeline Stamp (P659)
- What it does
- When to use
- What it does NOT do
- Related
Sekcje z nagłówków SKILL.md, w oryginale · 127 linii, 807 słów
Podgląd SKILL.md
---
name: park
description: "Park a feature on its branch without merging to main. Use when work is done but you're not ready to ship yet."
when_to_use: "When a feature is complete (or verified) on its branch but you want to defer merging. Triggered by /park, 'park this', 'done but don't merge yet'."
version: 1.0.0
---
# /park
Park a feature on its branch without merging. No review gates, no prompts — just a frontmatter stamp.
```
/park p665
```
---
## Pipeline Stamp (P659)
Before any other work in this skill:
1. Read spec frontmatter
2. Set `delivery_stage: park`
3. Append `park` to `pipeline_ran` inline list. Edit pattern: match `pipeline_ran: [existing, items]`, replace with `pipeline_ran: [existing, items, park]`. If `pipeline_ran` doesn't exist, add `pipeline_ran: [park]`. Always inline format.
4. **Predecessor check:** If `pipeline_plan` exists, find the skill before `park` in the plan. If that skill is NOT in `pipeline_ran` (exact match) → stop: "Run `/{predecessor}` first." Skip check if: (a) `pipeline_plan` absent, (b) this skill is first in plan, (c) `pipeline_ran` absent/empty and this is first planned skill.
5. If this skill is NOT in `pipeline_plan` → proceed silently (parking is always valid as an ad-hoc action).
---
## What it does
1. **Find the spec** — resolve P-number from argument. Look in `features/p{N}_*.md` in the feature worktree or main.
2. **Write park journal** — create `.claude/worktrees/.park-journal/pN.json` to enable crash recovery:
```bash
mkdir -p .claude/worktrees/.park-journal
echo '{"pn":"pN","spec_stamped":false,"kdd_captured":false,"branch_deleted":false}' \
> .claude/worktrees/.park-journal/pN.json
```
3. **Stamp spec (FIRST — before anything else)** — edit the spec frontmatter on the feature branch:
- `delivery_stage: park` (pipeline stamp already did this, but verify it's set)
- Commit the stamp on the feature branch (worktree pattern, `.claude/rules/git.md`): `git add features/pN_*.md && git commit -m "chore: park pN — stamp"`
- Update journal: `spec_stamped: true`
4. **Commit stamp to main** — use `git-ops.sh commit-to-main` to send the spec update to main. This acquires main.lock and commits atomically. From the **main repo root**:
```bash
cp .claude/worktrees/wN/features/pN_*.md features/ # copy stamped spec from worktree to main
./scripts/git-ops.sh commit-to-main \
--message "chore: park pN — stamp" \
--files features/pN_*.md
```
Update journal: `spec_stamped_main: true`.
4b. **Write the ship trigger into the spec — REQUIRED, not optional.** Directly under the spec's
title, a quoted block naming the date, who parked it, where the work lives, why it was not
shipped, and above all **the observable condition that should bring it back**:
```markdown
> **Parked YYYY-MM-DD (founder).** Built and passing its closure gate on branch `feature/pN-...`;
> worktree removed, branch kept. Not shipped because <reason>.
> **Ship trigger:** <the observable thing that must happen first>. Ship with `/ship pN`.
```
Without a trigger, parked work has no way back except someone remembering it — and `/day` prints
this line verbatim, so a missing trigger shows up as "(no ship trigger recorded — add one)".
4c. **Offer to archive the branch on the remote.** A parked branch lives on one laptop; the commits
are finished, reviewed work and the disk is the only copy. Pushing the **feature branch** to
`origin` touches neither `main` nor production.
**A push is never pre-approved** (`.claude/rules/git.md`) — ask in one line, and record the
answer in the park block ("branch archived on origin" / "local only, by choice"):
```bash
git push origin feature/pN-<slug> # only after the founder says so, in that turn
```
5. **KDD capture (optional)** — if user wants learnings captured:
- Run `/kdd` — invoke `/slava:maintain:kdd` to capture decisions into `docs/decisions.md`
- Commit KDD changes to main via:
```bash
./scripts/git-ops.sh commit-to-main \
--message "docs: park pN — kdd" \
--files docs/decisions.md
```
- Update journal: `kdd_captured: true`
6. **Abandon branch** — delete worktree + release slot lock via `git-ops.sh abandon`:
```bash
./scripts/git-ops.sh abandon wN --nonce "$CP_LOCK_NONCE_wN"
```
Update journal: `branch_deleted: true`
7. **Clean up journal** — delete `.claude/worktrees/.park-journal/pN.json`
8. **Report:**
```
P{N} parked. Stamp and KDD committed to main.
Worktree removed, slot released. Branch feature/p{N}-xxx KEPT (abandon never deletes it).
Archived on origin: yes / no — local only.
Ship trigger: <the condition written into the spec>.
Run /ship p{N} when ready to merge the feature code to main.
```
---
## When to use
- Feature is done on branch, you want to merge later (not now)
- Feature passed `/verify` but you're batching merges
- You're switching context and want to mark progress
## What it does NOT do
- Does not change `status:` — it stays whatever it was (`in-progress`, `qa`, etc.). `/day` knows
this: it skips `delivery_stage: park` when listing specs that are "waiting for you", and lists
parked ones separately with their ship trigger and no call to action. Before that filter existed,
P1181 asked to be shipped every morning for 16 days.
- Does not delete the branch. Step 6 removes the **worktree** and releases the slot;
`git-ops.sh abandon` keeps the branch and its commits.
- Does not merge anything
- Does not run reviews or tests
- Does not move the spec to `features/done/`
---
## Related
- `/dev` — implements the feature (stops at UAT gate on branch)
- `/verify` — live UAT (sets status: qa on pass)
- `/ship` — merges to main and closes the spec
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · slavochek2/claritypledge | 100 | AGPL-3.0 |
| technicalpickles/pickled-claude-plugins | 100 | MIT |
| xb1itz/unfry | 100 | MIT |
| hotdata-dev/claude-park | 92 | MIT |
| Fanar-labs/just-continue | 92 | MIT |
| SergioLizana/Dynamo | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 7abf4c1bcdfb (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
- 100pr
Otwiera pull request z dobrze napisanym opisem, gdy praca na gałęzi jest skończona i gotowa do przeglądu. - 100pr
Tworzy pull request z pełną walidacją, gdy praca jest gotowa do przekazania do przeglądu. - 100pr-create
Przeprowadza przez zatwierdzenie zmian, wypchnięcie gałęzi i utworzenie pull requesta, gdy praca jest gotowa do przeglądu. - 80Ship
Przygotowuje zmianę do czystego commita, PR i wydania, gdy implementacja jest gotowa i użytkownik chce ją wysłać. - 100finishing-a-development-branch
Weryfikuje i porządkuje ukończoną funkcję, a potem kieruje do scalenia, pull requestu, odłożenia lub odrzucenia, niczego nie niszcząc bez wyraźnego potwierdzenia. - 100ship
Zamyka sesję jednym ruchem: commituje, wysyła, zamyka beads i synchronizuje, gdy praca jest skończona.