ship-feature-e2elisted

Use when the user runs /ship-feature-e2e, pastes an existing GitHub issue (#N / URL), or says "ship this feature end to end", "implement this issue fully", "feature to main", "issue to PR to merge", "act then merge reinstall" — one feature or one issue through issue → worktree/branch → implement → unit + e2e happy paths → PR with summary + confidence 1–10 → local act → merge → reinstall. Orchestrate by loading and reusing sdlc-tasks-executions, organized-commits, finish-and-ship (and siblings); do not reimplement those skills. Prefer over finish-and-ship when merge/act/reinstall are in scope; over messy-repo-orchestrator for a single feature/issue.
YosefHayim/dufflebag · ★ 0 · Code & Development · score 69

Install: claude install-skill YosefHayim/dufflebag

# Ship Feature End-to-End **Orchestrator only.** One invocation → one feature **or** one existing issue landed on the default branch with proof. Slash: **`/ship-feature-e2e`**, then either freeform feature text **or** an existing issue (`#2`, full URL, `Fixes #2`). **Done** means: issue linked, topic branch/worktree, happy-path **unit** + **e2e** green, PR with short **Summary** + **Confidence 1–10**, local **act** green when CI exists, **merged** to default, product **reinstalled/proven**, done receipt. “PR open” alone is **not** done for this skill. ## Reuse first (mandatory) This skill **must not** reinvent sibling workflows. Before any step, **load the sibling `SKILL.md` and follow it** for that concern. Only implement glue those skills do not own (test hard-gates, confidence score, act, merge, reinstall, done receipt). | Concern | Load and follow | |---------|-----------------| | Single-lane issue + worktree + branch + cmux/brief + PR skeleton | `sdlc-tasks-executions` **setup-lanes** (exactly **one** lane) | | Atomic commits / history shape | `organized-commits` | | Verify, push, open/update PR, handoff hygiene (pre-merge) | `finish-and-ship` | | Multi-feature parallel cleanup | **Stop** — hand off to `messy-repo-orchestrator` (not this skill) | | Multi-feature **test-gap** campaign to main | **Stop** — hand off to `test-gap-ship` | | Live production deploy URL | `deploy-and-prove` after ship if user asks | | Browser-only local proof | `preview-and-prove` when the