← ClaudeAtlas

ship-parallellisted

Run ready code items through isolated git worktrees with a lazy-senior-dev build brief, gate-first review by one non-maker model, and partial-success merging. Use when ship batches ready code items or when the lean worktree build farm must resume, review, merge, or report a batch.
vraj-ai/skills · ★ 4 · Code & Development · score 73
Install: claude install-skill vraj-ai/skills
# Ship Parallel The worktree-isolated build farm composed by `ship`. Forked from `parallel` and kept lean: **one contributor, one reviewer, and the reviewer only runs if the gate is already green.** It never mutates `backlog.jsonl`. One item equals one branch and one worktree: ```text git worktree add -b ship/<slug>/<id> CONTEXT/worktrees/<slug>/<id> -> contributor builds to the ladder, commits -> ship runs the locked Verification-command -> green? one non-maker reviewer. red? straight back, no model spent -> merge to MAIN_BRANCH or report failure ``` The fixed contributor is `opencode-go/glm-5.2`. A model never reviews its own code. ## The ladder Pass this to every contributor, verbatim. It is the whole build brief. > **Work down these rungs in order. Stop at the first one that solves it.** > > 1. **Necessity** — does this need to exist at all? (YAGNI) > 2. **Codebase reuse** — is it already implemented in this project? > 3. **Standard library** — does the stdlib solve it? > 4. **Native platform** — can built-in features (CSS, HTML5 inputs, DB constraints) handle it? > 5. **Existing dependencies** — use what is installed before adding anything > 6. **One-liner** — can this be a single line? > 7. **Minimal implementation** — only now, write the smallest thing that works > > **Never simplify away:** input validation at trust boundaries, error handling > that prevents data loss, security measures, accessibility, or anything the > acceptance criteria explicitly as