CLAUDE-FORGE(1)

NAME

claude-forgeSupercharge Claude Code with 11 AI agents, 36 commands & 15 skills — the claude-code plugin framework inspired by…

SYNOPSIS

INFO

578 stars
128 forks
0 views

DESCRIPTION

Supercharge Claude Code with 11 AI agents, 36 commands & 15 skills — the claude-code plugin framework inspired by oh-my-zsh. 6-layer security hooks included. 5-min install.

README

Claude Forge

Turn Claude Code into a full development environment

MIT License Claude Code Stars Forks Contributors Last Commit

Quick StartWorkflowsWhat's InsideInstallationArchitectureCustomization한국어


What is Claude Forge?

Claude Forge is an open-source development environment for Claude Code that provides 11 specialized agents, 36 slash commands, 15 skill workflows, and 14 automation hooks. Often described as "oh-my-zsh for Claude Code", it transforms Claude Code from a basic CLI into a full-featured development environment. One install gives you agents, commands, skills, hooks, and 8 rule files -- all pre-wired and ready to go.

Think of it as oh-my-zsh for Claude Code: the same way oh-my-zsh enhances your terminal, Claude Forge supercharges your AI coding assistant.


⚡ Quick Start

# 1. Clone
git clone --recurse-submodules https://github.com/sangrokjung/claude-forge.git
cd claude-forge

2. Install (creates symlinks to ~/.claude)

./install.sh

3. Launch Claude Code

claude

install.sh symlinks everything to ~/.claude/, so git pull updates instantly.

If you find Claude Forge useful, please consider giving it a star -- it helps others discover this project.

New here?

If you're new to development or Claude Code, start with these:

StepWhat to do
1Run /guide after install -- an interactive 3-minute tour
2Read First Steps -- glossary + TOP 6 commands
3Browse Workflow Recipes -- 5 copy-paste scenarios

Or just type /auto login page and let Claude Forge handle the entire plan-to-PR pipeline for you.


🔄 Development Workflows

Feature Development Workflow

Real-world workflows that chain commands, agents, and skills together.

Feature Development

Build new features with a plan-first, test-first approach:

/plan → /tdd → /code-review → /handoff-verify → /commit-push-pr → /sync
graph LR
    P["/plan<br><small>Design & risk analysis</small>"] --> T["/tdd<br><small>Tests first, then code</small>"]
    T --> CR["/code-review<br><small>Quality & security check</small>"]
    CR --> HV["/handoff-verify<br><small>Fresh-context validation</small>"]
    HV --> CPR["/commit-push-pr<br><small>Commit, push, PR & merge</small>"]
    CPR --> S["/sync<br><small>Sync project docs</small>"]
style P fill:#533483,stroke:#fff,color:#fff
style T fill:#0f3460,stroke:#fff,color:#fff
style CR fill:#0f3460,stroke:#fff,color:#fff
style HV fill:#e94560,stroke:#fff,color:#fff
style CPR fill:#1a1a2e,stroke:#fff,color:#fff
style S fill:#16213e,stroke:#fff,color:#fff

StepWhat happens
/planAI creates an implementation plan. Waits for your confirmation before coding.
/tddWrite tests first, then code. One unit of work at a time.
/code-reviewSecurity + quality check on the code you just wrote.
/handoff-verifyAuto-verify build/test/lint all at once.
/commit-push-prCommit, push, create PR, and optionally merge -- all in one.
/syncSync project docs (prompt_plan.md, spec.md, CLAUDE.md, rules).

Bug Fix

Fast turnaround for bug fixes with automatic retry:

/explore → /tdd → /verify-loop → /quick-commit → /sync
StepWhat happens
/exploreNavigate the codebase to find where the bug lives.
/tddWrite a test that reproduces the bug, then fix it.
/verify-loopAuto-retry build/lint/test up to 3 times with auto-fix on failure.
/quick-commitFast commit for simple, well-tested changes.
/syncSync project docs after commit.

Security Audit

Comprehensive security analysis combining CWE and STRIDE:

/security-review → /stride-analysis-patterns → /security-compliance
StepWhat happens
/security-reviewCWE Top 25 vulnerability scan + STRIDE threat modeling.
/stride-analysis-patternsSystematic STRIDE methodology applied to system architecture.
/security-complianceSOC2, ISO27001, GDPR, HIPAA compliance verification.

Team Collaboration

Agent Teams Hub-and-Spoke

Parallel multi-agent execution for complex tasks:

/orchestrate → Agent Teams (parallel work) → /commit-push-pr
StepWhat happens
/orchestrateCreate an Agent Team with file-ownership separation and hub-and-spoke coordination.
Agent TeamsMultiple agents work in parallel on frontend, backend, tests, etc.
/commit-push-prMerge all work, verify, and ship.

Why Claude Forge?

Most developers either use Claude Code with no customization or spend hours assembling individual configs. Claude Forge gives you a production-ready setup in 5 minutes.

FeatureClaude ForgeBasic .claude/ SetupIndividual Plugins
Agents11 pre-configured (Opus + Sonnet)Manual setup requiredVaries by plugin
Slash Commands36 ready-to-useNonePer-plugin basis
Skill Workflows15 multi-step pipelinesNonePer-plugin basis
Security6-layer automated hooksNone by defaultPer-plugin basis
Installation5 min, one commandHours of manual configPer-plugin install
Updatesgit pull (instant)Manual per-filePer-plugin update
Workflow IntegrationEnd-to-end pipelines (plan to PR)Disconnected toolsNot integrated

📦 What's Inside Claude Forge

Claude Forge Components

CategoryCountHighlights
Agents11planner architect code-reviewer security-reviewer tdd-guide database-reviewer + 5 more
Commands36/commit-push-pr /handoff-verify /explore /tdd /plan /orchestrate /security-review ...
Skills15build-system security-pipeline eval-harness team-orchestrator session-wrap ...
Hooks14Secret filtering, remote command guard, DB protection, security auto-trigger, rate limiting ...
Rules8coding-style security git-workflow golden-principles agents interaction ...
MCP Servers6context7 memory exa github fetch jina-reader

📥 Claude Forge Installation Guide

Prerequisites

DependencyVersionCheck
Node.jsv22+node -v
Gitanygit --version
jqany (macOS/Linux)jq --version
Claude Code CLI≥1.0claude --version

macOS / Linux

git clone --recurse-submodules https://github.com/sangrokjung/claude-forge.git
cd claude-forge
./install.sh

The installer:

  1. Checks dependencies (node, git, jq)
  2. Initializes git submodules (CC CHIPS status bar)
  3. Backs up existing ~/.claude/ if present
  4. Creates symlinks for 7 directories + settings.json to ~/.claude/
  5. Applies CC CHIPS custom overlay
  6. Optionally installs MCP servers and external skills
  7. Adds shell aliases (ccclaude, ccrclaude --resume)

Because it uses symlinks, git pull in the repo updates everything instantly.

Windows

# Run PowerShell as Administrator
.\install.ps1

Windows uses file copies instead of symlinks. Re-run install.ps1 after git pull to update.

MCP Server Setup

ServerAPI KeySetup
context7Not requiredAuto-installed via install.sh
memoryNot requiredAuto-installed via install.sh
fetchNot requiredRequires uvx (Python)
jina-readerNot requiredAuto-installed via install.sh
exaOAuthclaude mcp add exa --url https://mcp.exa.ai/mcp
githubPATSet GITHUB_PERSONAL_ACCESS_TOKEN env var

Customization

Override settings without modifying tracked files:

cp setup/settings.local.template.json ~/.claude/settings.local.json
vim ~/.claude/settings.local.json

settings.local.json merges on top of settings.json automatically.


🏗 Claude Forge Architecture

Symlink Architecture

graph TB
    subgraph REPO["claude-forge (git repo)"]
        A["agents/ (11)"]
        C["commands/ (36)"]
        S["skills/ (15)"]
        H["hooks/ (14)"]
        R["rules/ (8)"]
        SC["scripts/"]
        CC["cc-chips/"]
        K["knowledge/"]
        REF["reference/"]
        SET["settings.json"]
    end

    INSTALL["./install.sh"]
    REPO --> INSTALL

    subgraph HOME["~/.claude/ (symlinked)"]
        HA["agents/"]
        HC["commands/"]
        HS["skills/"]
        HH["hooks/"]
        HR["rules/"]
        HSC["scripts/"]
        HCC["cc-chips/"]
        HSET["settings.json"]
    end

    INSTALL -->|symlink| HOME

    CLAUDE["claude (CLI)"]
    HOME --> CLAUDE

    style REPO fill:#1a1a2e,stroke:#e94560,color:#fff
    style HOME fill:#0f3460,stroke:#16213e,color:#fff
    style INSTALL fill:#e94560,stroke:#fff,color:#fff
    style CLAUDE fill:#533483,stroke:#fff,color:#fff
Full Directory Tree
claude-forge/
  ├── agents/               Agent definitions (11 .md files)
  ├── cc-chips/             Status bar submodule
  ├── cc-chips-custom/      Custom status bar overlay
  ├── commands/             Slash commands (28 .md + 8 SKILL dirs)
  ├── docs/                 Screenshots, diagrams
  ├── hooks/                Event-driven shell scripts (14)
  ├── knowledge/            Knowledge base entries
  ├── reference/            Reference documentation
  ├── rules/                Auto-loaded rule files (8)
  ├── scripts/              Utility scripts
  ├── setup/                Installation guides + templates
  ├── skills/               Multi-step skill workflows (15)
  ├── install.sh            macOS/Linux installer (symlinks)
  ├── install.ps1           Windows installer (copies)
  ├── mcp-servers.json      MCP server configurations
  ├── settings.json         Claude Code settings
  ├── CONTRIBUTING.md       Contribution guide
  ├── SECURITY.md           Security policy
  └── LICENSE               MIT License

🛡 Claude Code Automation Hooks

Security Hooks

6-Layer Security Defense

HookTriggerProtects Against
output-secret-filter.shPostToolUseLeaked API keys, tokens, passwords in output
remote-command-guard.shPreToolUse (Bash)Unsafe remote commands (curl pipe, wget pipe)
db-guard.shPreToolUseDestructive SQL (DROP, TRUNCATE, DELETE without WHERE)
security-auto-trigger.shPostToolUse (Edit/Write)Vulnerabilities in code changes
rate-limiter.shPreToolUse (MCP)MCP server abuse / excessive calls
mcp-usage-tracker.shPreToolUse (MCP)Tracks MCP usage for monitoring

Utility Hooks

HookTriggerPurpose
code-quality-reminder.shPostToolUse (Edit/Write)Reminds about immutability, small files, error handling
context-sync-suggest.shSessionStartSuggests syncing docs at session start
session-wrap-suggest.shStopSuggests session wrap-up before ending
work-tracker-prompt.shUserPromptSubmitTracks work for analytics
work-tracker-tool.shPostToolUseTracks tool usage for analytics
work-tracker-stop.shStopFinalizes work tracking data
task-completed.shTaskCompletedNotifies on subagent task completion
expensive-mcp-warning.sh-Warns about costly MCP operations

🤖 Claude Code Agents

Each agent has a color in the UI for quick visual identification:

Opus Agents (6) -- Deep analysis & planning

AgentColorPurpose
plannerblueImplementation planning for complex features and refactoring
architectblueSystem design, scalability decisions, technical architecture
code-reviewerblueQuality, security, and maintainability review
security-reviewerredOWASP Top 10, secrets, SSRF, injection detection
tdd-guidecyanTest-driven development enforcement (RED → GREEN → IMPROVE)
database-reviewerbluePostgreSQL/Supabase query optimization, schema design

Sonnet Agents (5) -- Fast execution & automation

AgentColorPurpose
build-error-resolvercyanFix build/TypeScript errors with minimal diffs
e2e-runnercyanGenerate and run Playwright E2E tests
refactor-cleaneryellowDead code cleanup using knip, depcheck, ts-prune
doc-updateryellowDocumentation and codemap updates
verify-agentcyanFresh-context build/lint/test verification

Color Semantics

ColorMeaning
blueAnalysis & review
cyanTesting & verification
yellowMaintenance & data
redSecurity & critical
magentaCreative & research
greenBusiness & success

📋 All Claude Forge Commands

36 Commands (click to expand)

Core Workflow

CommandDescription
/planAI creates implementation plan. Waits for confirmation before coding.
/tddWrite tests first, then code. One unit of work at a time.
/code-reviewSecurity + quality check on code you just wrote.
/handoff-verifyAuto-verify build/test/lint all at once.
/commit-push-prCommit, push, create PR, optionally merge -- all in one.
/quick-commitFast commit for simple, well-tested changes.
/verify-loopAuto-retry build/lint/test up to 3x with auto-fix.
/autoOne-button automation: plan to PR without stopping.
/guideInteractive 3-minute tour for first-time users.

Exploration & Analysis

CommandDescription
/exploreNavigate and analyze codebase structure.
/build-fixIncrementally fix TypeScript and build errors.
/next-taskRecommend next task based on project state.
/suggest-automationAnalyze repetitive patterns and suggest automation.

Security

CommandDescription
/security-reviewCWE Top 25 + STRIDE threat modeling.
/stride-analysis-patternsSystematic STRIDE methodology for threat identification.
/security-complianceSOC2, ISO27001, GDPR, HIPAA compliance checks.

Testing & Evaluation

CommandDescription
/e2eGenerate and run Playwright end-to-end tests.
/test-coverageAnalyze coverage gaps and generate missing tests.
/evalEval-driven development workflow management.
/evaluating-code-modelsBenchmark code generation models (HumanEval, MBPP).
/evaluating-llms-harnessBenchmark LLMs across 60+ academic benchmarks.

Documentation & Sync

CommandDescription
/update-codemapsAnalyze codebase and update architecture docs.
/update-docsSync documentation from source-of-truth.
/sync-docsSync prompt_plan.md, spec.md, CLAUDE.md + rules.
/syncPull latest changes and sync all project docs (prompt_plan.md, spec.md, CLAUDE.md, rules). Use after any workflow or at session start.
/pullQuick git pull origin main.

Project Management

CommandDescription
/init-projectScaffold new project with standard structure.
/orchestrateAgent Teams parallel orchestration.
/checkpointSave/restore work state.
/learnRecord lessons learned + suggest automation.
/web-checklistPost-merge web testing checklist.

Refactoring & Debugging

CommandDescription
/refactor-cleanIdentify and remove dead code with test verification.
/debugging-strategiesSystematic debugging techniques and profiling.
/dependency-upgradeMajor dependency upgrades with compatibility analysis.
/extract-errorsExtract and catalog error messages.

Git Worktree

CommandDescription
/worktree-startCreate git worktree for parallel development.
/worktree-cleanupClean up worktrees after PR completion.

Utilities

CommandDescription
/summarizeSummarize URLs, podcasts, transcripts, local files.

🧩 All Claude Forge Skills

15 Skills (click to expand)
SkillDescription
build-systemAuto-detect and run project build systems.
cache-componentsNext.js Cache Components and Partial Prerendering (PPR) guidance.
cc-dev-agentClaude Code development workflow optimization (context engineering, sub-agents, TDD).
continuous-learning-v2Instinct-based learning: observe sessions via hooks, create atomic instincts with confidence scoring.
eval-harnessFormal evaluation framework for eval-driven development (EDD).
frontend-code-reviewFrontend file review (.tsx, .ts, .js) with checklist rules.
manage-skillsAnalyze session changes, detect missing verification skills, create/update skills.
prompts-chatSkill/prompt exploration, search, and improvement.
security-pipelineCWE Top 25 + STRIDE automated security verification pipeline.
session-wrapEnd-of-session cleanup: 4 parallel subagents detect docs, patterns, learnings, follow-ups.
skill-factoryConvert reusable session patterns into Claude Code skills automatically.
strategic-compactSuggest manual context compaction at logical intervals to preserve context.
team-orchestratorAgent Teams engine: team composition, task distribution, dependency management.
verification-engineIntegrated verification engine: fresh-context subagent verification loop.
verify-implementationRun all project verify skills and generate unified pattern verification report.

Frequently Asked Questions

What is Claude Forge?

Claude Forge is an open-source development environment for Claude Code. It bundles 11 specialized agents, 36 slash commands, 15 skill workflows, 14 automation hooks, and 8 rule files into a single install. Think of it as "oh-my-zsh for Claude Code" -- it turns the basic Claude Code CLI into a fully equipped coding environment with built-in workflows for planning, TDD, security review, and deployment.

How is Claude Forge different from other Claude Code plugins?

Most Claude Code plugins solve one problem at a time. Claude Forge is a complete development environment -- agents, commands, skills, hooks, and rules that work together as a cohesive system. Instead of assembling individual plugins and configuring each one, Claude Forge gives you a pre-wired pipeline: /plan feeds into /tdd, which feeds into /code-review, which feeds into /handoff-verify, which feeds into /commit-push-pr. The 6-layer security hook system also runs automatically without extra configuration.

Is Claude Forge compatible with the official Claude Code plugin system?

Yes. Claude Forge installs via symlinks to ~/.claude/ and works alongside official Claude Code plugins. Your existing settings.local.json overrides are preserved, and you can add or remove individual components without affecting the rest of the system.

How do I update Claude Forge?

Run git pull in the claude-forge directory. Because the installer uses symlinks (on macOS/Linux), updates take effect immediately -- no re-install needed. On Windows, re-run install.ps1 after pulling to copy the updated files.

Does Claude Forge work on Windows?

Yes. Run install.ps1 in PowerShell as Administrator. Windows uses file copies instead of symlinks, so you need to re-run install.ps1 after each git pull to apply updates. All agents, commands, skills, and hooks work the same on Windows, macOS, and Linux.

What does /sync do?

/sync synchronizes your project's memory and documentation. It pulls the latest changes from the remote repository and then syncs all project docs -- prompt_plan.md, spec.md, CLAUDE.md, and rule files. Run it after completing any workflow (feature, bug fix, refactor) or at the start of a new session to ensure Claude has the latest context.

How does Claude Forge handle memory across sessions?

Claude Forge uses a 3-layer memory system:

  1. Project docs (CLAUDE.md, prompt_plan.md, spec.md) -- Project-level instructions and plans that persist in the repository. /sync keeps these up to date.
  2. Rule files (rules/) -- Coding style, security, workflow conventions loaded automatically each session.
  3. MCP memory server -- A persistent knowledge graph that stores entities and relations across sessions.

Running /sync at session start ensures layers 1 and 2 are current. The MCP memory server (layer 3) persists automatically.


🤝 Contributing

See CONTRIBUTING.md for guidelines on adding agents, commands, skills, and hooks.



Use Claude Forge? Show it!

[![Built with Claude Forge](https://img.shields.io/badge/Built_with-Claude_Forge-orange?style=flat-square)](https://github.com/sangrokjung/claude-forge)

Add this badge to your project's README to let others know you use Claude Forge.


Contributors


📄 License

MIT -- use it, fork it, build on it.

If Claude Forge improved your workflow, a star helps others find it too.


Made with ❤️ by QJC (Quantum Jump Club)

SEE ALSO

clihub3/4/2026CLAUDE-FORGE(1)