Cc Kit — Git skill for Claude Code

cc-kit

Set up Claude Code on any machine from a Git repo you own.

Keep your skills, hooks, agents, commands, CLAUDE.md sections and permission rules in one repository. On each machine, run `npx @mehmetmuejde/cc-kit`, pick what this machine should get, and cc-kit writes it into `~/.claude`. Change something in the repo, run `npx @mehmetmuejde/cc-kit update` everywhere, done.

npx @mehmetmuejde/cc-kit           # first run asks for your repo URL, then lets you pick
npx @mehmetmuejde/cc-kit update    # latest repo state, same selection, no questions

Or install it once and use the short command:

npm install -g @mehmetmuejde/cc-kit
cc-kit
cc-kit update

Why

• One source of truth. Your setup lives in Git, not scattered across machines.
• Per-machine choice. The client laptop doesn't get the skills of another client; the server may run kubectl apply, the laptop may not.
• No sync daemon, no hooks of its own. cc-kit runs when you run it and does nothing in between.

Repository layout

Everything is optional; empty categories are skipped.

skills//SKILL.md              plus any other files in that folder
agents/.md
commands/.md
hooks//hook.yaml              plus the script(s) it runs
claude-md/-.md            sections of CLAUDE.md, ordered by number
settings/base.yaml                  any other settings.json keys
settings/permissions/.yaml    named permission rule sets
cc-kit.yaml                         optional: name

Names starting with `_` or `.` are ignored.

Hooks

# hooks/bash-safety/hook.yaml
description: Blocks irreversible shell commands
default: true            # preselected in the picker
event: PreToolUse
matcher: Bash
if: "Bash(git commit*)"  # optional
command: python3 {{dir}}/bash-safety.py

`{{dir}}` becomes the installed folder, e.g. `~/.claude/hooks/bash-safety`. cc-kit registers the hook in `settings.json` for you.

CLAUDE.md sections