Files
ClaudeForge/docs/INSTALLATION.md
T
Claude e45065e8ba docs: refresh README/docs/examples + install scripts for waves 1-4
User-facing documentation drifted behind several waves of feature work
(plugin manifest, hooks, sync command, --weekly, audit skills, Karpathy
skill, CLAUDE.local.md tier, layered hook config). Refresh + fix one
real install bug. Surgical edits only — no rewrites.

README.md:
  - "What's New" block now reflects the plugin manifest, --weekly,
    InstructionsLoaded hook, AGENTS.md interop, CLAUDE.local.md tier,
    layered hook config, and the fail-closed guardian.
  - "What's Included" expanded from 5 numbered bullets to a structured
    list grouping the 5 skills (incl. three forked audit skills),
    2 slash commands, 1 agent, and 3 hook scripts.
  - Components Deep Dive: /sync-claude-md and the guardian's fail-closed
    contract now documented.
  - Project Status: 1.0.0 -> 2.1.0; Quick Stats updated to reflect
    actual component counts.
  - Acknowledgments: attribution to MIT-licensed forrestchang and
    shanraisshan source repos for adapted patterns.

docs/ARCHITECTURE.md, docs/QUICK_START.md, docs/TROUBLESHOOTING.md,
docs/INSTALLATION.md, examples/modular-setup.md, examples/integration-
examples.md:
  - Every "20-300 lines" / ">300 lines" / "exceeds 300 lines" reference
    rewritten to the actual 150-line hard cap.
  - Every ls/Remove-Item path that pointed at the legacy
    ~/.claude/commands/enhance-claude-md/ bundle now points at the
    top-level enhance-claude-md.md + sync-claude-md.md files.
  - integration-examples.md line-bounds shell guard now uses 20..150.

docs/CLAUDE.md:
  - Install-verify ls list extended with the three new audit-skill
    directories so docs match what install.sh actually creates.

install.sh + install.ps1 (REAL FIX, not just docs):
  - The three forked audit skills (claude-md-drift-audit, link-check,
    dependency-rescan) were registered in plugin.json but never copied
    by the direct-install path. Both installers now iterate over them
    after the karpathy-guidelines block, mirroring the same backup +
    nested-duplicate-cleanup pattern. Banner section and uninstall
    instructions list all 5 skills.

Verified:
  - All 5 CLAUDE.md files in this repo still <= 150 lines after edits.
  - install.sh passes bash -n syntax check.
  - Plugin manifest still resolves all 8 referenced paths on disk.
  - README invariants present: 2.1.0, --weekly, hooks/hooks.json,
    both source-repo attributions, three audit skill names.
  - Stale-claim sweep: zero "20-300" / ">300" / "exceeds 300" refs
    remain in docs/ or examples/.
2026-05-19 02:04:00 +00:00

8.4 KiB

Installation Guide

Complete installation instructions for ClaudeForge on all supported platforms.


Prerequisites

Required

  • Claude Code 2.0 or later
  • Operating System: macOS, Linux, or Windows
  • Git (for change detection by guardian agent)
  • Terminal access (macOS/Linux) or PowerShell (Windows)

Installation Methods

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/alirezarezvani/ClaudeForge/main/install.sh | bash

Windows (PowerShell as Administrator)

iwr https://raw.githubusercontent.com/alirezarezvani/ClaudeForge/main/install.ps1 -useb | iex

What this does:

  1. Downloads the installer script
  2. Prompts for installation scope (user-level or project-level)
  3. Copies all components to appropriate directories
  4. Creates backups of any existing installations
  5. Optionally installs quality hooks

Method 2: Manual Git Clone

# Clone the repository
git clone https://github.com/alirezarezvani/ClaudeForge.git

# Navigate to directory
cd ClaudeForge

# Run installer
./install.sh  # macOS/Linux
# or
.\install.ps1  # Windows

Method 3: Manual Installation (Advanced)

If you prefer to manually copy files:

Step 1: Download Components

Download the latest release from: https://github.com/alirezarezvani/ClaudeForge/releases

Step 2: Choose Installation Scope

User-Level (Recommended) - Available in all Claude Code projects:

# macOS/Linux
INSTALL_DIR="$HOME/.claude"

# Windows
$INSTALL_DIR="$env:USERPROFILE\.claude"

Project-Level - Available only in current project:

# macOS/Linux
INSTALL_DIR="./.claude"

# Windows
$INSTALL_DIR=".\.claude"

Step 3: Copy Components

# Create directories
mkdir -p "$INSTALL_DIR/skills"
mkdir -p "$INSTALL_DIR/commands"
mkdir -p "$INSTALL_DIR/agents"

# Copy skill
cp -r skill "$INSTALL_DIR/skills/claudeforge-skill"

# Copy slash command
cp -r command "$INSTALL_DIR/commands/enhance-claude-md"

# Copy guardian agent
cp agent/claude-md-guardian.md "$INSTALL_DIR/agents/"

Step 4: Restart Claude Code

Close and restart Claude Code to load the new components.


Installation Scopes

User-Level Installation

Location: ~/.claude/ (or %USERPROFILE%\.claude on Windows)

Advantages:

  • Available in all Claude Code projects
  • Install once, use everywhere
  • Automatic updates apply globally

Use When:

  • You work on multiple projects
  • You want consistent CLAUDE.md standards across all projects
  • You're the primary developer on your machine

Project-Level Installation

Location: ./.claude/ (in your project root)

Advantages:

  • Project-specific configuration
  • Version controlled with project (can commit to git)
  • Team members get same tools

Use When:

  • Different projects need different versions
  • You want to version control the tools
  • Team collaboration requires shared tooling

Verification

After installation, verify all components are installed correctly:

Check Skill Installation

# macOS/Linux
ls -la ~/.claude/skills/claudeforge-skill/

# Windows
dir $env:USERPROFILE\.claude\skills\claudeforge-skill\

Expected output:

analyzer.py
generator.py
template_selector.py
validator.py
workflow.py
SKILL.md
README.md
examples/

Check Command Installation

# macOS/Linux
ls -la ~/.claude/commands/enhance-claude-md.md ~/.claude/commands/sync-claude-md.md

# Windows
dir $env:USERPROFILE\.claude\commands\enhance-claude-md\

Expected output:

enhance-claude-md.md
README.md

Check Agent Installation

# macOS/Linux
ls -la ~/.claude/agents/claude-md-guardian.md

# Windows
dir $env:USERPROFILE\.claude\agents\claude-md-guardian.md

Test in Claude Code

  1. Restart Claude Code
  2. Open any project
  3. Run the command:
    /enhance-claude-md
    
  4. You should see the multi-phase workflow start

Quality Hooks (Optional)

During installation, you'll be asked if you want to install quality hooks.

What are Quality Hooks?

  • Pre-commit validation that checks CLAUDE.md quality before commits
  • Ensures best practices compliance
  • Only available for project-level installations

To Install Hooks:

# During installer
# When prompted: "Would you like to install quality hooks?"
# Type: y

# Or manually:
mkdir -p .claude/hooks
cp hooks/pre-commit.sh .claude/hooks/
chmod +x .claude/hooks/pre-commit.sh

To Use Hooks:

Configure git to use the hook:

# Add to .git/config or use git config
git config core.hooksPath .claude/hooks

Troubleshooting Installation

Issue: "Installation files not found"

Cause: Running installer from wrong directory

Solution:

cd ClaudeForge  # Navigate to repository root
./install.sh     # Run from correct directory

Issue: "Permission denied"

Cause: Installer doesn't have execute permission

Solution:

chmod +x install.sh  # macOS/Linux
# or run with bash explicitly
bash install.sh

Issue: "~/.claude directory not found"

Cause: Claude Code not installed or hasn't been run yet

Solution:

  1. Ensure Claude Code is installed
  2. Run Claude Code at least once to create directory structure
  3. Or let installer create directories (it will prompt)

Issue: Command not recognized after installation

Cause: Claude Code hasn't reloaded components

Solution:

  1. Fully quit Claude Code (not just close window)
  2. Restart Claude Code
  3. Wait a few seconds for components to load
  4. Try command again: /enhance-claude-md

Issue: "Skill not found" error

Cause: Skill directory name mismatch

Solution:

# Verify skill directory name is exactly:
ls ~/.claude/skills/
# Should show: claudeforge-skill

# If different, rename:
mv ~/.claude/skills/old-name ~/.claude/skills/claudeforge-skill

Issue: Windows installer fails with execution policy error

Cause: PowerShell execution policy restricts scripts

Solution:

# Run PowerShell as Administrator
# Set execution policy temporarily:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

# Then run installer:
.\install.ps1

Updating ClaudeForge

To update to a newer version:

Method 1: Using Installer

# Pull latest changes
cd ClaudeForge
git pull origin main

# Run installer (existing installation will be backed up)
./install.sh

Method 2: Manual Update

# Backup current installation
mv ~/.claude/skills/claudeforge-skill ~/.claude/skills/claudeforge-skill.backup

# Copy new version
cp -r skill ~/.claude/skills/claudeforge-skill

# Repeat for command and agent

Uninstallation

To completely remove ClaudeForge:

User-Level Uninstall

# macOS/Linux
rm -rf ~/.claude/skills/claudeforge-skill
rm -rf ~/.claude/commands/enhance-claude-md
rm -f ~/.claude/agents/claude-md-guardian.md

# Windows (PowerShell)
Remove-Item -Recurse -Force $env:USERPROFILE\.claude\skills\claudeforge-skill
Remove-Item -Recurse -Force $env:USERPROFILE\.claude\commands\enhance-claude-md
Remove-Item -Force $env:USERPROFILE\.claude\agents\claude-md-guardian.md

Project-Level Uninstall

# macOS/Linux
rm -rf ./.claude/skills/claudeforge-skill
rm -rf ./.claude/commands/enhance-claude-md
rm -f ./.claude/agents/claude-md-guardian.md
rm -rf ./.claude/hooks  # If quality hooks were installed

# Windows (PowerShell)
Remove-Item -Recurse -Force .\.claude\skills\claudeforge-skill
Remove-Item -Recurse -Force .\.claude\commands\enhance-claude-md
Remove-Item -Force .\.claude\agents\claude-md-guardian.md
Remove-Item -Recurse -Force .\.claude\hooks

After uninstalling, restart Claude Code.


Next Steps

After successful installation:

  1. Read Quick Start Guide: QUICK_START.md
  2. Test the command: Run /enhance-claude-md in a project
  3. Review Architecture: ARCHITECTURE.md
  4. Explore Examples: Check examples/ directory

Support

If you encounter installation issues not covered here:


Installation successful? Proceed to Quick Start Guide