Installing cckit

FlowCommand

Put the cckit command on your PATH and confirm it works. Setting it up in a repo comes next.

cckit is pure bash over git, gh, and jq. There is no build step — installing it puts the cckit dispatcher on your PATH, the list of folders your terminal searches when you type a command. Pick whichever route fits.

Install globally

1. Pick an install method. Each tab is one route — pick the one that fits, and copy the box.

   One-liner

   macOS · Linux · WSL — no npm or brew

   curl -fsSL https://cckit.dev/install.sh | bash

   Homebrew

   Formula/cckit.rb

   brew install jeiemgi/cckit/cckit

   npm

   the bare name is taken, so cckit is scoped

   npm install -g @jeiemgi/cckit

   From source

   symlinks bin/cckit onto your PATH

   git clone https://github.com/jeiemgi/cckit.git
   cd cckit && ./scripts/install.sh

2. Verify it’s on your PATH.

   cckit version       # prints the installed version
   cckit doctor        # preflight: git/gh/jq present, gh authenticated

cckit install [bin-dir] symlinks bin/cckit into the first writable PATH folder (~/.local/bin, then /usr/local/bin, then ~/bin), or a folder you pass.

It is a symlink, not a copy — the dispatcher resolves the link back to the repo, so git pull upgrades your install with no reinstall.

Dependencies

Required	Why
git, gh, jq	the lifecycle (worktrees, GitHub, JSON)
bash 3.2+	the dispatcher + lib

Optional, auto-detected, never required:

Optional	Enables
tmux	cckit orchestrate (parallel panes)
glow / fzf / gum	nicer terminal output and pickers
Node + Chrome	cckit debug (browser debugging via chrome-devtools-axi)

cckit doctor reports what’s missing.

What is a symlink? (skip if you know)

A symlink is a pointer file: it stands in one folder but redirects to a file somewhere else. cckit installs as a symlink into a PATH folder that points back to the cloned repo, so updating the repo updates your installed command automatically.

Next steps

Installing only puts cckit on your PATH — nothing has touched a repo yet. Where to go from here:

Initialize cckit Set it up in a repo: cckit scan to see what's there, then cckit init to scaffold cckit.config.json + .claude/.

Adopt an existing repo Already have kit-shaped files? Record them instead of overwriting.

Claude Code & other agents How cckit ships as a Claude Code plugin, and how any agent drives the same CLI through AGENTS.md.

Security & secret guard The local gate and pre-commit hook that block secrets, keys, and your private data before they leave your machine.