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.

Two branches of this skill sit outside that core, and say 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. prepare runs the commands a repository declares for a new worktree, and it chooses none of them itself: a repository that declares nothing gets the install its lockfile implies and no more. Nothing else in this file depends on either branch.

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