← ClaudeAtlas

claude-autoshiplisted

Chains implement → verify → review → ship after a feature plan is approved. Reads the plan for the current branch, runs the full pipeline in one session, and stops on any failure or non-minor review finding. Use when asked to "autoship", "ship this feature end to end", or "run the chain". Do NOT auto-trigger. Requires an approved plan file.
erclx/toolkit · ★ 1 · AI & Automation · score 77
Install: claude install-skill erclx/toolkit
# Claude autoship Chain the post-plan pipeline in a single run. Every step has a stop condition. State is always recoverable on stop: code lives on the branch, review output on disk, plan still linked. ## Guards - All `.claude/plans/` and `.claude/review/` reads resolve at the main worktree root, not the current worktree. See Worktrees in `CLAUDE.md`. - Run `git branch --show-current` and replace `/` with `-` to derive `<slug>`. If empty, stop: `❌ Detached HEAD. Checkout the feature branch first.` - If `.claude/plans/feature-<slug>.md` does not exist at the main worktree root, stop: `❌ No approved plan at .claude/plans/feature-<slug>.md. Run /claude-feature first.` - If the working tree has uncommitted changes unrelated to the plan, stop: `❌ Uncommitted changes outside the plan. Commit or stash before autoshipping.` ## Step 0: enter a worktree If `git rev-parse --git-dir` equals `git rev-parse --git-common-dir`, the session is in the main worktree. Invoke `toolkit:claude-worktree` before continuing. The wrapper handles name derivation and branch alignment. Do not call `EnterWorktree` directly. If neither command resolves, stop: `❌ Not a git repository. Autoship needs git or a WorktreeCreate hook.` If the two commands differ, the session is already in a linked worktree. Continue. ## Step 1: read the plan Read `.claude/plans/feature-<slug>.md` at the main worktree root. This file is the scope for this run. ## Step 2: implement Implement only what the plan describes.