Skip to main content

Claude Code Integration

This repo has small helpers that keep Claude Code's settings in sync with git secret and stay diff-clean. They run automatically via the pre-commit hook; you can also invoke them directly.

Tip 24.1: sync-claude-deny​

Reads tracked paths from .gitsecret/paths/mapping.cfg and adds them to Claude Code's permissions.deny list in .claude/settings.json. Prevents Claude from accidentally reading or editing secret files.

sync-claude-deny             # update settings.json in place
sync-claude-deny --check     # exit non-zero if settings.json would change (CI / hook use)

From bin/sync-claude-deny.

Tip 24.2: sort-claude-settings​

Sorts arrays in .claude/settings.json so git diff is stable across runs (no order churn).

sort-claude-settings         # rewrite settings.json with sorted arrays

From bin/sort-claude-settings.

Tip 24.3: Pre-Commit Automation for Claude Code​

hooks/pre-commit runs both helpers above automatically when you commit changes that could affect Claude Code's settings:

  • Touching .gitsecret/paths/mapping.cfg → runs sync-claude-deny and re-stages the resulting .claude/settings.json.
  • Touching .claude/settings.json → runs sort-claude-settings and re-stages it.
  • Adding or removing an alias, function or bin/ script without staging anything under tips/ → prints an advisory reminder (never blocks).

So you never end up with stale deny rules or shuffled settings arrays in commits. The hook does other things too (e.g. doctoc + markdownlint on staged markdown) — see hooks/pre-commit for the whole picture. Symlinked into .git/hooks/pre-commit by init/12_git_hooks.sh.

Tip 24.4: Shared config and skills in ~/.claude​

Everything under claude/ is symlinked into ~/.claude/ by init/52_macos_claude.sh, so every machine gets the same Claude Code context from one place:

  • claude/CLAUDE.md → ~/.claude/CLAUDE.md — global instructions loaded into every session.
  • claude/skills/ → ~/.claude/skills/ — reusable skills, one directory per skill with a SKILL.md.
  • claude/statusline-command.sh → ~/.claude/statusline-command.sh.

Only these entries are linked; machine-local state (projects/, sessions/, history.jsonl) stays untouched. Anything already at one of those paths is moved into backups/ first, and the run tells you so.

Add a skill by creating claude/skills/<name>/SKILL.md with name and description front-matter. Because skills/ is linked as a directory, it shows up in ~/.claude immediately — no need to re-run dotfiles.