Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

ship

/ship

Wdraża brief Hamster: scala gałąź bazową, implementuje etapami równolegle, testuje, przegląda i tworzy commity, a PR otwiera po pytaniu.

Repozytorium
cli ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

98/ 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.
Higiena13 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
7
Skrypty
2
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/ensure-ready.ps1, scripts/ensure-ready.sh

Co robi i kiedy

Wdraża brief Hamster: scala gałąź bazową, implementuje etapami równolegle, testuje, przegląda i tworzy commity, a PR otwiera po pytaniu.

Oryginalny opis (EN)

Ship a Hamster brief. Merge the base branch, implement in parallel waves, test, review, and create bisectable commits. Ask before opening a PR. Use when the user wants to execute or ship an existing brief.

Jak działa

  1. Readiness
  2. Setup
  3. Brief Selection and Scheduling
  4. Branch + Merge Base
  5. Execution and Completion
  6. Error Recovery
  7. Notes
Sekcje z nagłówków SKILL.md, w oryginale · 113 linii, 1 079 słów
Podgląd SKILL.md
---
name: ship
description: Ship a Hamster brief. Merge the base branch, implement in parallel waves, test, review, and create bisectable commits. Ask before opening a PR. Use when the user wants to execute or ship an existing brief.
---

# Ship Brief

Executes a Hamster Studio brief. **Execution-only**: the plan — parent tasks, subtasks, context — was generated upstream in Hamster Studio and synced into `.hamster/`. This skill schedules those existing tasks into parallel waves and executes them. It never generates, splits, or replans tasks on its own initiative — but it doesn't execute blindly either. Executors adapt to mechanical drift (documented as deviations) and escalate genuine plan defects as **PLAN_ISSUE** instead of implementing something known to be wrong; the orchestrator (and for scope changes, the user) decides how to proceed.

Project skills ARE loaded during execution: task-executors read `.claude/skills/hamster-project-context/SKILL.md` when it exists (generated by `hamster sync`; clients that discover `.claude/skills/` expose it as the `hamster-project-context` skill), relevant project skills, and `.hamster/` blueprints/methods. Execution-only restricts *planning*, not *context*.

**Argument**: "$ARGUMENTS"
If empty or literally `$ARGUMENTS`, use the brief the user named.

---

## Readiness

Before assuming a Hamster CLI, run this skill's bundled gate. Set `SKILL_DIR` to the absolute path of the directory holding the SKILL.md you just read — the shell's working directory is the user's project, not this skill — and keep the whole command on one line with its statements `;`-separated, because some clients flatten a fenced block before running it. The `else` branch is the same gate inline, for clients that expose no readable path to the installed package.

Unix:

```bash
SKILL_DIR="<absolute path of the directory containing this SKILL.md>"; if [ -f "$SKILL_DIR/scripts/ensure-ready.sh" ]; then bash "$SKILL_DIR/scripts/ensure-ready.sh"; else export PATH="$HOME/.hamster/bin:$PATH"; if command -v hamster >/dev/null 2>&1 && { status_err="$(hamster --no-tui status 2>&1)"; printf '%s' "$status_err" | grep -q "Logged in" || { printf '%s\n' "$status_err" >&2; false; }; } && sync_err="$(hamster sync 2>&1)"; then echo READY; else [ -n "${sync_err:-}" ] && printf '%s\n' "$sync_err" >&2; echo SETUP_NEEDED; exit 1; fi; fi
```

Windows:

```powershell
$SkillDir = "<absolute path of the directory containing this SKILL.md>"; if (Test-Path "$SkillDir\scripts\ensure-ready.ps1") { pwsh "$SkillDir\scripts\ensure-ready.ps1" } else { $env:PATH = "$env:USERPROFILE\.hamster\bin;" + $env:PATH; if (Get-Command hamster -ErrorAction SilentlyContinue) { $status = & hamster --no-tui status 2>&1 | Out-String; if ($LASTEXITCODE -eq 0 -and $status -cmatch "Logged in") { $syncOut = & hamster sync 2>&1; if ($LASTEXITCODE -eq 0) { "READY" } else { [Console]::Error.WriteLine(($syncOut | Out-String).TrimEnd()); "SETUP_NEEDED"; exit 1 } } else { [Console]::Error.WriteLine($status.TrimEnd()); "SETUP_NEEDED"; exit 1 } } else { "SETUP_NEEDED"; exit 1 } }
```

If it prints `SETUP_NEEDED` in Codex on macOS and `hamster` is already on `PATH`, re-run only this readiness command with elevated permission. The default workspace sandbox cannot read Keychain credentials, and an extra directory grant does not change that. If the elevated check prints `READY`, continue. Only if it still prints `SETUP_NEEDED`, run this plugin's `setup` skill, then re-run the check. Do not continue until it prints `READY`.

## Setup

Read [brief-selection](references/brief-selection.md) and run **Account Resolution** first. On `ACCOUNT_UNRESOLVED`, follow its team-selection/re-sync guidance and stop. Then run prerequisites and live sync in ONE bash call, assigning `account` to the resolved filesystem slug (shell-quoted), not `HAMSTER_ACCOUNT_ID`:

```bash
export PATH="$HOME/.hamster/bin:$PATH"
errors=""
command -v hamster >/dev/null 2>&1 || errors="${errors}hamster CLI not found. Run this plugin's setup skill.\n"
[ -d ".hamster" ] || errors="${errors}.hamster/ directory not found. Run 'hamster sync' first.\n"
command -v gh >/dev/null 2>&1 || errors="${errors}gh CLI not found. Install from https://cli.github.com\n"
dirty=$(git status --porcelain 2>/dev/null | head -5)
[ -n "$dirty" ] && errors="${errors}Uncommitted changes:\n${dirty}\n"
if [ -n "$errors" ]; then printf "PREREQ_FAIL:\n$errors"; exit 1; fi
account="<resolved filesystem account slug>"
repo=$(git rev-parse --show-toplevel 2>/dev/null)
watch=""
for pid in $(pgrep -f "hamster sync .*--watch" 2>/dev/null); do
  cwd=$(lsof -a -d cwd -p "$pid" -Fn 2>/dev/null | sed -n 's/^n//p' | head -1)
  [ -z "$cwd" ] && cwd=$(readlink "/proc/$pid/cwd" 2>/dev/null)
  [ "$cwd" = "$repo" ] && { watch="existing"; break; }
  [ -z "$cwd" ] && watch="unknown"
done
if [ -n "$watch" ]; then echo "PREREQ_OK account=${account} sync_pid=${watch}"
else hamster sync --watch > /dev/null 2>&1 & echo "PREREQ_OK account=${account} sync_pid=$!"; fi
```

- `PREREQ_FAIL` → show errors and stop (for uncommitted changes only: ask whether to proceed or stash)
- `sync_pid=existing` → a watcher whose working directory is this repo is already running (an interrupted session, or the user's own). Reuse it; do NOT kill it at completion
- `sync_pid=unknown` → a watcher exists but its working directory could not be read, so it may belong to another repo. Advisory only: reuse it rather than starting a second one, and never kill it
- Numeric `sync_pid` → remember the literal number. Each Bash call is a fresh shell, so `$sync_pid` does not survive to later calls — at Completion, substitute it literally (e.g. `kill 12345`)

---

## Brief Selection and Scheduling

Follow **Brief Selection** and **Scheduling** in [brief-selection](references/brief-selection.md): argument parsing, the brief picker, the inline frontmatter parse, and wave grouping, ending with the single execute/modify/cancel confirmation.

---

## Branch + Merge Base

One call:

```bash
lowest_id=$(ls "$tasks_dir"/*.md 2>/dev/null | xargs -n1 basename | grep -oE '^[a-z][a-z0-9]*-[0-9]+' | sort -t- -k2,2n | head -1)
branch="feature/${lowest_id}-${slug}"
git checkout -b "$branch"
default_branch=$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name 2>/dev/null || echo "main")
git fetch origin "$default_branch" && git merge "origin/$default_branch" --no-edit
echo "branch=$branch base=$default_branch"
```

Merge conflict → **STOP**, report conflicts, do NOT auto-resolve.

---

## Execution and Completion

Read [execution-loop](references/execution-loop.md) and follow it for every wave: parallel execution, the validate/test gate, wave review, bisectable per-parent commits, and the progress report — then its Completion section for the watcher shutdown, final validation, optional PR, and brief status update.

---

## Error Recovery

| Error | Recovery |
|-------|----------|
| Prereq failure | Stop with instructions (uncommitted changes: ask stash/proceed) |
| Account unresolved | Stop; follow Account Resolution's team-selection/re-sync guidance |
| Brief not found | Show partial matches, ask user |
| Auth expired | `hamster auth login`; continue without status updates if it fails |
| Merge conflict (base or between executors) | Stop, report, never auto-resolve |
| Test gate fails | Stop, report, ask fix or skip |
| NEEDS_FIXES after 2 rounds | Report to user, ask skip or manual fix |
| Worker fails | Report, ask retry or skip |
| Executor returns PLAN_ISSUE | Verify: resolved authority-correct work → review; unresolved local fix → corrected re-launch; scope beyond authority or unresolved decision → ask user |
| Task already done | Skip it |

## Notes

- One commit set per parent (subtasks are never committed individually)
- Interrupted? `/hamster:resume-hamster` reconstructs state from git + task statuses
- Single PR per brief by default; >15 tasks → ask about splitting
Pliki w paczce (7)
  • SKILL.md 8 KB
  • references/brief-selection.md 9 KB
  • references/execution-loop.md 10 KB
  • references/agents/task-executor.md 11 KB
  • references/agents/wave-reviewer.md 6 KB
  • scripts/ensure-ready.ps1 1 KB
  • scripts/ensure-ready.sh 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · gethamster/cli98MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
namedtoaster/the-last-mile100MIT
rjmurillo/ai-agents100MIT
ericrisco/rsc-harness100MIT
zahidakhyar/skills100MIT
NolwennD/gabier100Apache-2.0
mgiovani/cc-arsenal100MIT

Migawka bazy z 13.11.2026 · wersja paczki 4236d75d2bd4 (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

  • 98plan-hamster
    Analizuje istniejący brief i plan przed budową: mapuje zależności zadań i grupuje pracę w równoległe fale.
  • 100review-hamster
    Przegląda kod w dwóch przejściach: najpierw krytyczne problemy blokujące wdrożenie, potem sugestie informacyjne, a poprawki wprowadza po akceptacji użytkownika.
  • 100relay-ship
    Prowadzi pełny przepływ wydania: scala bazę, uruchamia testy, przegląda diff, podnosi wersję, commituje, wypycha i tworzy pull request.
  • 100dev-ship
    Wypycha gałąź, uruchamia wszystkie zestawy testów, otwiera lub aktualizuje pull request i obserwuje CI, ale nigdy nie scala.
  • 100branch-commit-pr
    Tworzy nazwaną gałąź, robi commity w konwencji Conventional Commits, wysyła ją i otwiera pull request na GitHubie.
  • 100create-pr
    Otwiera nowy pull request dla gałęzi zadania (sprawdza gałąź bazową, commity, zgłoszenie i push) lub aktualizuje tytuł i opis istniejącego PR według konwencji Penpot.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.