gitkit

One place where the git facts live that every other skill in a toolchain keeps re-deriving: where a worktree goes and what it's named, how it is created, adopted, and removed, which branch is the base, and when to rebase versus merge.

The core here is not clever. All of it is native git worktree, with no vendor CLI, no GUI dependency, and no recorded state anywhere but git's own. That is the point: a laptop with a desktop dev tool and a headless Linux box run identical commands, so there is no second code path to keep in sync and no "degraded mode" to reason about.

One branch of this skill sits outside that core, and says so. Stacked branches drive GitHub's gh stack extension, so that branch alone needs gh and a GitHub remote. It degrades to plain git rather than failing, and nothing else in this file depends on it, so a box with no gh runs everything above untouched.

gitkit is a primitives skill. Most of its runs come from another skill calling it, not from a human saying its name.

When this fires

• worktree. "Spin up a worktree for this branch", "make me a worktree for #42", "where is the worktree for issue-42-…", "tear down this worktree", "list my worktrees".
• base ref. "What's the base branch here", "diff me against the base".
• sync. "Should I rebase or merge here", "sync this branch with main", "this branch is behind, bring it up to date", "make this PR review-ready on the latest base".
• clean. "Clean up my merged worktrees", "which branches can I delete", "this repo is full of dead branches".
• rescue. "I lost a commit", "my rebase ate my work", "I reset the wrong branch", "what's in this stash".
• stack. "Stack this on #43", "start #44 on top of #43's branch", "restack this chain", "show me the stack".
• called by another skill. Any skill that needs a worktree, a base ref, a branch name, or a sync decision delegates here and uses what comes back.