Adapters
cckit is split in two: an agnostic core that does every operation, and per-agent adapters that route a specific agent to it — so any agent can drive cckit while Claude Code gets a native feel.
The two layers
Section titled “The two layers”| Layer | What it is | Depends on an agent? |
|---|---|---|
| Core | Pure bash that owns every operation | No |
| Adapter | The thin layer a specific agent uses to discover and call the core | Yes — one per agent |
Understanding this split is the key to extending cckit to a new agent.
The agnostic core
Section titled “The agnostic core”The core is pure bash plus the standard toolchain (git, gh, jq, tmux). It owns every operation — the GitHub work lifecycle, efforts, worktrees, orchestration, garbage collection — and nothing in it is specific to any agent.
| Path | Role |
|---|---|
bin/cckit | The CLI dispatcher — one entrypoint for every verb |
scripts/lib/*.sh | The operations (start/pr/close, effort, worktree, gc, orchestrate, …) |
scripts/*.sh | The runnable ops (publish, migrate, doctor, digest, …) |
cckit.config.json | The only source of repo / owner / base-branch — nothing is hardcoded |
The contract the core exposes to agents lives in AGENTS.md: every verb, its arguments, and its --llm output. An agent that can run a shell and parse the output can drive the whole lifecycle through this contract alone.
Adapter one — Claude Code
Section titled “Adapter one — Claude Code”The Claude adapter is the native layer that makes cckit feel built-in inside Claude Code. It is a thin shell over the core — it adds discovery and ergonomics, never a second copy of an operation.
| Path | Role |
|---|---|
.claude-plugin/plugin.json | The Claude Code plugin manifest (install entrypoint) |
commands/*.md | Slash commands (/kit-*) that front the core verbs |
skills/* | Skills that teach Claude how and when to run each operation |
templates/{agents,hooks,rules,skills,settings} | What cckit init scaffolds into a project’s .claude/ |
Every command and skill ultimately calls a core verb or a scripts/lib function. There is one implementation of each operation (in the core); the adapter only routes Claude to it. This is why a fix in the core is a fix for every agent at once.
Claude and Codex support
Section titled “Claude and Codex support”Effort #257 establishes shared behavior and release checks for Claude Code and Codex. The compatibility inventory records current gaps and the acceptance scenarios each adapter must pass. Native Codex support is being implemented; shell access alone does not establish behavioral parity.
Other adapters
Section titled “Other adapters”Any other agent (Copilot, Antigravity, a custom model) is a future adapter over the same core. An adapter is whatever that agent needs to discover and call the verbs — at minimum, the agent reads AGENTS.md and shells out with --llm.
No adapter re-implements an operation; they all target the one core contract. Deeper per-agent adapters (native command palettes, richer prompts) are follow-ups. The agnostic CLI contract is the floor every agent already stands on.
Why the split
Section titled “Why the split”- One source of truth. An operation lives once, in the core. No drift between “the Claude way” and “the CLI way”.
- Portable. The core has no agent dependency, so cckit runs in CI, a cron job, or a bare terminal — not only inside an agent.
- Open to any agent. Adding an agent is writing an adapter, not forking the kit.
Independent, educational project — not affiliated with or endorsed by Anthropic. Claude and Claude Code are trademarks of Anthropic PBC.Disclaimer & trademarks ·
From Mexico withloveby josegtz