How to set up cckit in a Git repo with Claude Code

FlowConversational

❯_

Do this with Claude CodeCopy a prompt that links the cckit docs so Claude learns the CLI, then follows these steps.

Copy as Markdown

Before you start

Install cckitQuickstart: your first lifecycle

This tutorial

Beginner4 min readNeedsgitgh (authenticated)jq

What you’ll set up: cckit reads everything from a single cckit.config.json. In three commands it scaffolds that config and a .claude/ folder, preflights your dependencies and GitHub auth, and shows you the stack it detected — so you know it’s ready before you run any real work. You describe the goal; Claude Code triggers the commands.

Steps

1. Ask Claude to set it up. You don’t name the commands — describe the intent.

   Prompt to paste

   Set up cckit in this repository and confirm it's ready to use. Scaffold its config,
   check my GitHub access, and show me what it detected about the stack.

2. cckit scaffolds the config. Under the hood it runs:

   cckit init     # scaffold cckit.config.json + .claude/
   cckit doctor   # preflight: deps + gh auth
   cckit scan     # show the detected stack + kit state

3. Verify it’s ready. doctor prints a green check for git, gh (authenticated), and jq; scan prints the detected language and framework. If both look right, cckit is live in the repo.

How it works

cckit is portable by design — no company, framework, or repo is baked in. Everything it needs comes from cckit.config.json, which init scaffolds and every other verb reads. That’s why setup is just “scaffold, preflight, confirm”: once the config exists and your tools are present, every later command resolves against it.

Nothing above the kit is touched

init only adds cckit’s own files. Your existing project layout is left exactly as it is.

Troubleshooting

doctor says gh isn’t authenticated. Run gh auth login once, then re-run the setup prompt. cckit uses your existing GitHub CLI session; it never stores a token of its own.

scan detected the wrong stack. The detection is a starting point you can correct — open cckit.config.json and adjust the project fields; every verb will pick up the change.

jq is missing. cckit degrades gracefully without optional tools, but jq is required for the JSON paths. Install it (brew install jq / your package manager) and re-run doctor.

Related tutorials

Take a GitHub issue to a merged PR The core lifecycle, one issue end to end.

Add cckit to an existing repo Bring cckit to a project that already has structure.

Drive Claude Code headless in CI Consume cckit as pure JSON from a bot.