Commands
gkit uses noun-style subcommands, in two layers.
SSH key layer — start here
Every workflow begins with an ssh identity: you need a key on the host before you
can clone anything. This layer is repo-independent — it manages keys and the
gkit-owned ~/.ssh/git_users.
| Command | Summary |
|---|---|
key | Generate id_<alias> ssh keys, copy a public key, and manage ~/.ssh/git_users. |
Repo layer — the everyday loop
Once a key is in place, these act on git repositories (a single repo or a whole fleet from a conf):
| Command | Summary |
|---|---|
init | Scaffold a starter clone conf in the current directory. |
clone | Clone the repos in a conf file, with hooks and transparent commands. |
stamp | Re-apply a conf’s post-clone over existing repos (e.g. stamp config on a late-added submodule). |
logoff | Gate: is every repo + submodule committed and pushed? |
stmb | Switch to the base branch and delete a finished feature once verified merged (reachability or patch-id content match), recursively. |
fixsub | Fix submodule metadata: un-detach each onto its .gitmodules branch (report, don’t yank, a feature branch) and inherit the root identity. |
Run gkit <command> --help for the authoritative flag list.