Tags

Every coloured tag in these docs says how a thing is triggered. This is the directory: each tag explains how you use it, then lists everything of that kind. New to the colours? The how-to-read guide introduces them.

One question sorts every tag: who pulls the trigger? You act, the system fires on its own, an agent reads the machine surface — or nothing triggers it and it’s simply a term worth knowing.

Conversational

Conversational

How you use it: just say what you want to Claude Code in plain words — no command, no slash. Asking to “contribute this upstream” starts the kit-contribute skill; “write docs for this” starts kit-docs-writer. Claude matches your intent to the right skill.

Skills cckit ships The conversational skills — kit-docs-writer, kit-customize, kit-contribute.

Driving cckit from agents How plain-language requests map to cckit verbs.

Command

Command

How you use it: type it in your terminal — cckit <verb> (for example cckit start 42). Run cckit help for the full list, or cckit <verb> --help for one. Add --llm to any verb for machine-readable output.

CLI reference Every cckit verb, flag, and --llm mode.

Quickstart cckit init, start, pr, sync, gc — the first lifecycle.

The GitHub cycle The command for each step of one issue.

Wave cckit wave + cckit watch — the parallel loop.

Skill

Skill

How you use it: in Claude Code, type / then the skill name — /kit-next, /kit-ship. The editor lists them as you type. Many skills also trigger conversationally (see above), so you can either run /kit-contribute or just ask to “contribute this upstream”.

Skills cckit ships The full list, grouped by what you're trying to do.

Flow

Flow

How you use it: you don’t trigger a flow directly — it’s the end-to-end process the commands and skills carry out. You “use” it by running its steps in order (each step has its own command). The diagrams on these pages draw each flow left to right.

The GitHub cycle Issue → branch → PR → review → merge.

Efforts, waves & worktrees Many issues at once, sorted into waves.

Wave A wave of issues fanned out to parallel agents.

Hook

Hook

How you use it: you don’t — a hook runs automatically when an event happens (before a commit, on session start, and so on). cckit wires them when you set up a repo; you just see the result. The Hooks page lists each one and the command it guards.

Hooks Every hook cckit wires, the event it fires on, and the command it guards.

Agent

Agent

How you use it: add --llm to any cckit verb to get machine-readable output (uniform data as TOON, JSON otherwise) — this is the surface an agent reads instead of scraping human text. The AGENTS.md contract documents it.

Driving cckit from agents The --llm surface and the AGENTS.md contract.

Concept

Concept

How you use it: nothing to trigger — a concept is a term worth knowing before you go further (an effort, a wave, a worktree). Click through to where it’s defined.

Efforts, waves & worktrees Efforts, sub-issues, waves, worktrees — defined.

How to read this guide The tags and diagrams, explained once.