How to extend Claude Code with cckit skills

SkillConversational

❯_

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

Beginner5 min readNeedscckit installed & initializedClaude Code

What you’ll do: a skill is a packaged instruction set Claude Code can run. cckit installs a set covering the whole lifecycle — the everyday loop, one-issue tasks, efforts, maintenance, and authoring. You run each with a / slash command, and many also trigger when you just describe the task in plain words.

Steps

1. See what’s installed. cckit init scaffolds the skills into the project. In Claude Code, type / to list them — they’re prefixed kit- (for example /kit-next, /kit-ship, /kit-effort-new).

2. Run one by slash command or by description. Type the skill directly, or just say what you want — a conversational skill triggers from plain intent:

   Two ways to trigger the same skill

   /kit-ship
   — or —
   Take this request all the way to a merged PR.

3. Add your own. Use kit-customize to add or edit agents and skills in a project, and kit-contribute to open a PR that sends your additions upstream.

How it works

Every skill maps to a job in the lifecycle: kit-next picks up the next unblocked issue, kit-ship goes from one request to merged, kit-effort-new creates a parent plus sub-issues, kit-gc prunes merged branches, kit-security-sweep audits for injection/auth/CORS issues. Skills marked conversational also fire from plain description — asking to “contribute this upstream” starts kit-contribute without you typing the slash command.

Running a skill

In Claude Code, type / and the skill name (for example /kit-next). See the full list on the Skills cckit ships reference page.

Troubleshooting

The /kit- skills don’t show up. They’re scaffolded by cckit init. Run it in the repo, then reload Claude Code so it picks up the new skills.

A conversational skill didn’t trigger. Be explicit — name the job clearly, or just run the slash command directly (/kit-contribute) instead of relying on phrasing.

I want a project-specific skill. Use kit-customize to add one in the project; it lives alongside the shipped skills and you can send it upstream with kit-contribute.

Related tutorials

Let Claude Code debug a web page A command-driven capability skills build on.

Take a GitHub issue to a merged PR What /kit-ship runs end to end.

Break a big feature into an effort What /kit-effort-new sets up.