メニュー
End-to-end delivery for a user request — fix the issue, then run the full kit cycle (start → PR → CI → merge → close → update kit) using the kit-task commands. One command takes an open issue from code to merged-on-base with the board kept in sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | kit-ship |
| description | End-to-end delivery for a user request — fix the issue, then run the full kit cycle (start → PR → CI → merge → close → update kit) using the kit-task commands. One command takes an open issue from code to merged-on-base with the board kept in sync. |
| when_to_use | When the user says "fix |
Takes one issue from open → implemented → merged on the base branch → closed → kit refreshed,
chaining the existing kit-task commands. This is the orchestrator that wraps the manual sequence,
with the sharp edges baked in (see Hard rules). Plugin-direct — the kit-task skills it chains
resolve from ${CLAUDE_PLUGIN_ROOT}.
| Field | Required | Notes |
|---|---|---|
| Issue number | ✓* | 157. *If the user gives a request with no issue, create one first via /kit-task-new, then proceed. |
| Skip merge | optional | --pr-only → stop after the PR (don't merge). Default merges. |
| # | Step | Command / action |
|---|---|---|
| 1 | Read the issue | gh issue view <N> — understand scope. If ambiguous/large/decision-heavy → stop and ask (don't ship blind). |
| 2 | Start | /kit-task-start <N> --worktree — branch <kind>/<N>-<slug> from the fresh base branch, mark In Progress. |
| 3 | Implement | Do the actual work to the issue's acceptance criteria, following project conventions + the relevant agent's domain. |
| 4 | Verify locally | Run the affected workspace's build / typecheck / lint (e.g. pnpm -F <pkg> build typecheck) or bash -n for scripts. Don't open a PR on red. |
| 5 | PR | /kit-task-pr <N> — commit, push, open PR to the base branch, mirror labels/milestone, add to board, move issue In Review. |
| 6 | Wait for CI | If the project has a required check, poll until it's not pending (background until loop). Pending ≠ failing — wait; never force-merge. |
| 7 | Merge | /kit-task-pr-merge once green — squash to the base, switch to base, pull, delete local+remote branch + worktree. |
| 8 | Close | gh issue close <N> + set board Done. Required when Closes #N does NOT auto-fire (PRs that merge to a non-default branch don't trigger GitHub auto-close). |
| 9 | Update kit (only if the change touched the plugin source) | bump version (/kit-dev ship) + /plugin update. |
Report at the end: issue state, PR number + merged status, branch cleaned, board reflects Done.
Autonomous execution under hard caps — run ONE long objective hands-off, OR drive the planned effort/flow set in parallel. On an APPROVED plan the captain DECIDES, MERGES each wave, and CONTINUES; it pings the human ONLY on a genuine blocker. THIN wrapper over the built-in /loop + the kit's orchestrate scripts; never a new engine.
Close an effort in ONE op — snapshot each sub-issue's diff BEFORE squash (work record), capture/judge/sync effort metrics, squash-merge the effort PR, close the parent + ALL native sub-issues, set the board Status=Done for each, garbage-collect the worktree/branch, run the optional knowledge-ingest hook, and finish with the kit-sync drift check.
Start an effort — thin caller of `cckit effort start <N>`. Creates the `effort/<N>-<slug>` integration branch + isolated bootstrapped worktree from the base branch, then marks the parent issue In Progress on the board. Sub-issues later branch from this effort branch or commit directly on it.
Start work on a GitHub issue — thin caller of `cckit start <N>`. Creates an isolated, bootstrapped worktree + `<kind>/<N>-<slug>` branch from the base branch and marks the issue In Progress on the board (if enabled). Worktree-first — there is no in-place mode.
Create an effort — a parent GitHub issue using the effort-model template (Goal / Scope / For agents / Verification) plus N native GitHub sub-issues linked via the sub-issues REST API, all added to the project board. The parent issue IS the plan.
Open the ONE pull request for an effort — `effort/<N>` → base branch — with a rich human-facing review body plus a `## For agents` section listing the file paths/entry points. Title `[Role] [#N] <title>`. Inherits labels + milestone from the parent issue and moves it to In Review on the board.
