ship
/ship
Przeprowadza zespół crew od planu do commita: plan, krytyka, wdrożenie, testy, recenzja i dokumentacja, z podsumowaniem.
- Autor
- dzusill ↗
- Repozytorium
- claude-crews ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.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
Przeprowadza zespół crew od planu do commita: plan, krytyka, wdrożenie, testy, recenzja i dokumentacja, z podsumowaniem.
Oryginalny opis (EN)
Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.
Jak działa
- 0. Triage
- 1. Plan (crew:planner, for non-trivial work)
- 1b. Challenge (crew:skeptic, whenever the planner ran)
- 2. Implement
- 3. Test (crew:tester)
- 4. Review (crew:reviewer)
- 5. Docs (crew:docs-writer, only when the user-facing surface changed)
- 6. Hand back to the user
Podgląd SKILL.md
---
name: ship
description: Runs the crew workflow end-to-end for a feature or fix. Plans, has the skeptic challenge the plan, implements, tests, reviews and documents using the crew agents, then hands back a summary and a commit message for approval. Use when the user asks to build, implement or fix something non-trivial with the crew, or invokes /crew:ship.
---
# Ship with the crew
You, the main session, orchestrate. **Subagents don't see this conversation.** Every brief you send must be self-contained: the repo path, the goal, the exact files or packages, the acceptance criteria and the constraints.
Task: $ARGUMENTS
## 0. Triage
- **Pick the coder by repo type:**
- `pom.xml` + `plugin.yml` (Paper/Spigot/Velocity) → `crew:plugin-coder`
- TypeScript web (Next.js, NestJS, Prisma, Expo) → `crew:web-coder`
- Visual or UI-heavy work → `crew:ui-builder`, which can pair with `web-coder` for the data and API side
- **Tiny, clear change** (1–2 files) → skip the planner.
- **Unclear requirement** → ask the user with AskUserQuestion before spending agent time.
## 1. Plan (`crew:planner`, for non-trivial work)
- Brief the planner with the task as the user stated it, the repo path and any constraints.
- Read the plan critically. Put product-level open questions to the user before any code is written.
- Carry assumptions the user didn't confirm into the final summary.
## 1b. Challenge (`crew:skeptic`, whenever the planner ran)
- Brief the skeptic with the user's task verbatim, the repo path and the full plan.
- **GO:** continue.
- **GO WITH CHANGES:** fold the 🔴 and 🟠 objections into the plan.
- **RETHINK:** stop and show the user the plan and the objections before writing code.
- Show the user the plan with the skeptic's verdict in 5–10 lines and wait for an OK before implementing. This is the checkpoint: no long unattended runs.
## 2. Implement
- Brief each coder with:
- the goal
- its plan steps
- the exact files and packages
- the acceptance criteria
- the constraint: no commits, no deploys
- **Parallelize only disjoint work.** Example: `web-coder` on `apps/api` while `ui-builder` builds `apps/web` against an agreed contract or types. Work in the same files stays sequential.
## 3. Test (`crew:tester`)
- Brief the tester with the changed files (from the coder reports or `git diff --name-only`) and the acceptance criteria.
- If the tester reports production bugs:
1. Send its findings verbatim to the coder.
2. After the fix, re-run the tester on the affected area.
## 4. Review (`crew:reviewer`)
- Brief the reviewer with the scope ("uncommitted changes in <repo>", or `<base>...HEAD`) and a 3-line plan summary.
- On **CHANGES REQUIRED**:
1. The coder fixes the 🔴 and 🟠 findings.
2. The tester re-runs the affected tests.
3. The reviewer re-checks only the fixes.
- Run at most **2 loops**. After that, stop and put the remaining items to the user.
## 5. Docs (`crew:docs-writer`, only when the user-facing surface changed)
Use the docs-writer for new or changed:
- commands and permissions
- config, messages or GUI keys
- placeholders
- API, env or setup steps
- architecture worth a `CLAUDE.md` update
## 6. Hand back to the user
- What was built (2–4 lines) and the files changed.
- Test results and the review verdict.
- Assumptions made and follow-ups.
- Proposed Conventional Commit message(s), matching the repo's `git log` style and language. Use one commit per logical change.
- **Do not commit, push or deploy until the user approves.** Keep commits meaningful.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · dzusill/claude-crews | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| namedtoaster/the-last-mile | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| zahidakhyar/skills | 100 | MIT |
| NolwennD/gabier | 100 | Apache-2.0 |
| mgiovani/cc-arsenal | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 4e9c6cea66f0 (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
- 100crew-ship
Wprowadza zmianę o ustalonym zakresie przez natywne misje phux, izolowane worktree, niezależny przegląd i autoryzowaną publikację, gdy lider Crew zleca prace implementacyjne. - 86check
Sprawdza niezacommitowane zmiany, gałąź lub PR z zespołem: tester uruchamia testy, recenzent ocenia kod, a wynik to decyzja, czy można zatwierdzić. - 86check
Sprawdza niezacommitowane zmiany, gałąź lub PR z zespołem: tester uruchamia testy, recenzent ocenia kod, a wynik to decyzja, czy można zatwierdzić. - 100workflow-build-feature
Buduje funkcję od początku do końca: specyfikacja i TDD, implementacja, testy jednostkowe, kontrola Playwright i pull request. - 82import
Prowadzi przez import eksportu z innego komputera: pyta o plik i decyduje z użytkownikiem o każdym projekcie i obszarze. - 95crew
Referencja poleceń crew: projekty, worktree, serwery deweloperskie, powiązania środowisk oraz uruchamianie Claude lub edytora.