菜单
Garbage-collect the repo — prune worktrees whose PR already merged, delete merged local + remote branches, surface orphan/unpushed commits and stale stashes, and flag issues whose PR merged but stayed open. Dry-run by default; destructive steps require explicit confirmation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | kit-gc |
| description | Garbage-collect the repo — prune worktrees whose PR already merged, delete merged local + remote branches, surface orphan/unpushed commits and stale stashes, and flag issues whose PR merged but stayed open. Dry-run by default; destructive steps require explicit confirmation. |
| when_to_use | When the repo has accumulated stale branches, orphan worktrees, or stashes (the SessionStart hygiene hook flags this), or on demand to tidy before/after a chapter of work. Replaces the manual cleanup sweep. |
Plugin-direct skill — helpers resolve from ${CLAUDE_PLUGIN_ROOT}.
Cleans what accumulates: merged-but-undeleted branches (local + remote), orphan worktrees, stale stashes, orphan unpushed commits, and stale-open issues.
Safety contract: read-only analysis first → present a plan → only delete
after the user confirms. Never touch: the base branch (main/develop), branches
with an open PR, worktrees of an open-PR branch, a branch/worktree whose
associated issue is still OPEN, or branches/commits whose work is not on the base
branch's remote (orphan work is surfaced, never auto-deleted).
Worktree↔issue association. A branch
<kind>/<N>-<slug>(or worktree dir<kind>+<N>-<slug>) belongs to issue #N — derived from the name, not registered.gcresolves #N and refuses to remove anything whose issue is still open, even with no PR yet — this protects in-progress worktrees that haven't opened a PR. Helper:${CLAUDE_PLUGIN_ROOT}/scripts/lib/worktree-issue.sh(wt_issue_number,wt_protected_reason).
# Read-only analysis lives in the CANONICAL Family-1 home — the skill is a thin caller (#419):
# scripts/lib/kit-gc.sh :: kit_gc_analyze (also what `kit gc` + the kit-ui cockpit run)
source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/kit-config.sh" && load_kit_config
KIT_GC_REPO="$KIT_REPO" source "${CLAUDE_PLUGIN_ROOT}/scripts/lib/kit-gc.sh"
kit_gc_analyze # worktrees / branches / stashes, each tagged PROTECTED/SAFE/ACTIVE/ORPHAN
Classify every branch/worktree (issue-open protection wins over everything except an explicit force):
| Bucket | Rule | Action |
|---|---|---|
| Protected (open issue) | wt_protected_reason non-empty — associated issue #N still OPEN | keep — never prune, even with no PR / merged PR |
| Safe to delete | PR MERGED, level with its remote (no unpushed commits), and issue closed/absent | prune |
| Active | open PR, or the base branch, or a worktree branch with an open PR | keep |
| Orphan | local commits not on the base branch's remote and no merged PR | surface, never auto-delete — offer to open a recovery PR |
For squash-merged branches, --is-ancestor is unreliable — trust the PR state, then verify the branch is level with its remote (git rev-list --count origin/<b>..<b> = 0) before deleting.
Print a table: worktrees to remove, branches to delete (local + remote), orphans to recover, stashes to drop, and stale-open issues (PR merged but issue still open). Ask for confirmation before any destructive step. Let the user veto per-bucket.
# Worktrees whose PR merged
git worktree remove <path> --force && git worktree prune
# Merged branches — local then remote
git branch -D <branch>
git push origin --delete <branch>
# Stale-open issues (PR already merged)
gh issue close <n> --repo "$KIT_REPO" --reason completed --comment "Delivered via PR #<pr>."
# Stashes — only after showing each diff and getting an explicit OK
git stash drop 'stash@{n}' # or: git stash clear
For each orphan branch with unique unpushed work: do not delete. Recover it
into a clean PR off the base branch (branch from $BASE, git checkout <orphan> -- <paths>, commit, push, open PR) so the user decides merge vs close.
main/develop) or an open-PR branch/worktree.wt_protected_reason non-empty) — close the issue first, or pass an explicit per-item override.