Skip to content
luiseiman edited this page Apr 5, 2026 · 5 revisions

dotforge

Configuration factory for Claude Code — bootstrap, audit, sync, and maintain .claude/ across projects.

GitHub stars Version License: MIT

What is dotforge?

dotforge generates and maintains the .claude/ configuration folder for your projects: rules, hooks, permissions, agents, and commands. It detects your tech stack, applies the right configuration, and keeps it in sync as the template evolves.

Quick Navigation

Page Description
Installation Setup guide (one-time + per-project)
Commands Reference All /forge commands + /cap alias
Stacks 15 technology stacks (auto-detected, composable)
Audit System Scoring formula, checklist, security cap
Agents 7 specialized subagents
Hooks Security and quality hooks
Practices Pipeline Continuous improvement workflow
Config Validation Measure if your config is effective
Plugin System Generate and distribute plugins
Export & Integrations Cursor, Codex, Windsurf, OpenClaw
MCP Templates MCP server config templates
Model Routing Agent model selection criteria
Architecture Internal component map
FAQ Common questions
Changelog Version history

Numbers

  • 17 skills — init, bootstrap, audit, sync, diff, reset, export, capture, update, watch, scout, insights, rule-check, benchmark, plugin, domain-extract, mcp-add
  • 7 agents — researcher, architect, implementer, code-reviewer, security-auditor, test-runner, session-reviewer
  • 15 stacks — auto-detected and composable (includes hookify and trading)
  • 5 hooks — block-destructive, lint-on-save, session-report, warn-missing-test, check-updates
  • 12-item audit — scored 0-10 with security cap

Demo

Command Demo
/forge init init demo
/forge bootstrap bootstrap demo
/forge audit audit demo
/forge status status demo

Internal analysis docs: docs/internal/ — cross-repo reverse engineering, 36-item improvement plan, feature flags reference.

Clone this wiki locally