claude-kit

**[English](#dotforge)** | **[Español](#dotforge-español)**

dotforge

[](https://github.com/luiseiman/dotforge/stargazers) [](LICENSE) [](VERSION) [](https://github.com/luiseiman/dotforge/commits/main)

Configuration governance for [Claude Code](https://docs.anthropic.com/en/docs/claude-code). Bootstrap, audit, sync, and evolve your `.claude/` configuration across projects — all markdown + shell scripts, zero required dependencies.

bootstrap → audit → sync → capture → propagate
    ↑                                    │
    └────────────────────────────────────┘

For people and teams managing more than one Claude Code project.

Use dotforge if:

• your .claude/ configuration drifts across repos
• you want to audit configuration quality, not just generate files once
• you want to propagate improvements discovered in one project to others
• you want a repeatable system, not a loose collection of prompts

Do not use dotforge if:

• you only have one small repo
• you only want a CLAUDE.md generator
• you do not care about sync, audit history, or cross-project consistency

Quick Start

# One-liner install
curl -fsSL https://raw.githubusercontent.com/luiseiman/dotforge/main/install.sh | bash

# Or manual:
git clone https://github.com/luiseiman/dotforge.git ~/.dotforge
export DOTFORGE_DIR="$HOME/.dotforge"
$DOTFORGE_DIR/global/sync.sh

# In any project directory:
/forge init         # Zero to config in one command
/forge audit        # Score your configuration (0-10)
/forge sync         # Update against current template

Requirements

bash (macOS, Linux, WSL). Git Bash works but WSL recommended on Windows. Optional: `python3`, `jq` for full hook support.

Works with

dotforge manages your `.claude/` configuration. It complements, not replaces, other tools:

Tool	What it does	How dotforge helps

...