Showcase

A short visual tour of cckit — each shot is a real command run for real, captured at the same size. For the full command list (copyable), see the CLI reference; to see how the verbs fit together, start with the GitHub cycle.

Where do I run these — and do they do the work?

These are plain terminal commands you type in your own shell (Terminal, iTerm, the VS Code terminal — anywhere). Typing cckit <verb> runs it and does the job itself: deterministic bash, no AI in the loop. They are not prompts that ask Claude to act.

cckit can also be driven by Claude Code and other agents — but that’s a separate surface. Every screenshot below is the CLI executing for real in a terminal.

Run it and you'll see human output — agents get something leaner

Run any of these yourself and you’ll see friendly, human-readable output. For agents, cckit keeps that output small on purpose: it borrows axi’s idea of protecting the context window — encoding results as TOON with a thin layer on top, so machine output costs a fraction of the tokens. A dedicated gh-axi integration is on the roadmap.

The installed version

cckit version

Detect this repo’s stack + kit state

cckit scan

Thin dashboard — board, worktrees, handoff

cckit status

Plan N parallel flows (dry-run)

cckit orchestrate --dry-run 46 47 48

Compact uniform JSON into TOON

echo '[…uniform array…]' | cckit encode-context