open source · MIT license

oh-my-zsh
for Claude Code

Turn Claude Code into a full development environment

11 Agents
36 Commands
15 Skills
6 Security Layers
Terminal
# Install in 5 minutes
$ git clone --recurse-submodules https://github.com/sangrokjung/claude-forge.git
$ cd claude-forge && ./install.sh
 
# Launch and explore
$ claude
> /guide
Welcome to Claude Forge! Let me show you around...

What's Inside

Everything you need for professional Claude Code development, pre-configured and ready to use.

🤖
11 agents

Specialized Agents

6 Opus-tier agents for deep analysis (planner, architect, code-reviewer, security-reviewer, TDD guide, database reviewer) and 5 Sonnet-tier agents for fast execution.

  • planner
  • code-reviewer
  • security-reviewer
  • tdd-guide
36 commands

Slash Commands

From planning to deployment. Chain commands into workflows or use /auto for full plan-to-PR automation.

  • /plan
  • /tdd
  • /code-review
  • /commit-push-pr
  • /auto
🛡
6-layer defense

Security Hooks

Secret filtering, remote command guard, SQL injection prevention, code change scanning, rate limiting, and MCP usage tracking. All automatic.

  • output-secret-filter
  • remote-command-guard
  • db-guard
  • security-auto-trigger
15 skills

Skill Workflows

Multi-step workflows combining agents, commands, and tools. Build systems, security pipelines, eval harnesses, and team orchestration.

  • build-system
  • security-pipeline
  • team-orchestrator
  • verification-engine
📐
8 rule files

Coding Rules

Always-on instructions that enforce coding style, security practices, git conventions, TDD, and evidence-based completion.

  • coding-style
  • security
  • git-workflow
  • golden-principles
🔗
symlink-based

Instant Updates

Everything is symlinked from the git repo to ~/.claude/. Run git pull and your entire environment updates. No reinstall needed.

  • git pull = instant update
  • settings.local.json overrides
  • fork-friendly

Quick Start

From zero to a fully-equipped Claude Code environment in 3 steps.

01

Clone

Clone the repository with submodules.

02

Install

Run install.sh to create symlinks.

03

Code

Launch claude and start building.

Terminal
# Clone with submodules
$ git clone --recurse-submodules https://github.com/sangrokjung/claude-forge.git
$ cd claude-forge
 
# Install (backs up existing ~/.claude/ automatically)
$ ./install.sh
 
# Launch Claude Code with all features
$ claude
> /guide

Prerequisites: Node.js v22+, Git, jq, Claude Code CLI >= 1.0

Development Workflows

Pre-built command pipelines for common development patterns.

Feature Development

/plan /tdd /code-review /handoff-verify /commit-push-pr

Bug Fix (Fast Path)

/explore /tdd /verify-loop /quick-commit

Security Audit

/security-review /stride-analysis-patterns /security-compliance

Full Autopilot

/auto login page Plan to PR, fully automated

How It Compares

Claude Forge vs. manual setup vs. starting from scratch.

Feature Claude Forge Manual Setup Vanilla Claude Code
Specialized agents 11 pre-built DIY
Slash commands 36 commands DIY
Security hooks 6-layer defense DIY
Workflow pipelines Pre-built chains DIY
Coding rules 8 rule files DIY
MCP servers 6 pre-configured DIY
Auto-updates git pull Manual N/A
Setup time 5 minutes Hours/days 0 minutes

FAQ

Common questions about Claude Forge.

Will this break when Claude Code updates?
Claude Forge uses stable extension points: ~/.claude/agents/, commands/, hooks/, rules/, and settings.json. These are documented conventions, not internal APIs. Anthropic has been adding to these, not breaking them. We test against each CLI update.
Does it work on Windows?
Yes. Windows uses install.ps1 which creates file copies instead of symlinks. You need to re-run install.ps1 after git pull. The agents, commands, hooks, and rules are identical across platforms.
Can I customize the agents and commands?
Absolutely. Fork the repo and modify any markdown file. For per-user overrides without touching tracked files, use settings.local.json. You can also add your own agents and commands alongside the built-in ones.
What if I already have a ~/.claude/ directory?
The installer automatically backs up your existing ~/.claude/ directory before creating symlinks. Your config is safe. You can restore it at any time.
Is this just a collection of dotfiles?
It started that way, but it's evolved beyond config files. It includes workflow orchestration (commands chain into pipelines), real-time security hooks (6-layer defense), multi-step skills with conditional logic, team orchestration with parallel agents, and instant updates via symlinks.
What are the prerequisites?
Node.js v22+, Git, jq (macOS/Linux), and Claude Code CLI >= 1.0. The installer checks all dependencies before proceeding.
How do I contribute?
See CONTRIBUTING.md in the repository. You can add agents, commands, skills, hooks, or documentation. PRs are welcome.