evolve-install

claude-evolve Install

This is the setup command for claude-evolve. Run it once after installing the plugin to verify Python dependencies, create a virtual environment if needed, and confirm the MCP server is registered.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Flag Parsing

Check for flags in the user's invocation:

• --help → Show Help Text (below) and stop
• --force → Skip Pre-Setup Check, run full setup from scratch
• --verify → Only run the verification phase (Phase 4), skip install/env setup
• --local → Install into a project-local .venv
• --global → Use the system Python (no venv)
• No flags → Auto-detect and run full setup if needed

Help Text

When user runs with --help, display this and stop:

claude-evolve Install - Set up evolutionary code discovery plugin

USAGE:
  /evolve-install              Install or verify (auto-detect)
  /evolve-install --local      Install into a project-local .venv
  /evolve-install --global     Use system Python (no venv)
  /evolve-install --verify     Only verify existing install
  /evolve-install --force      Force full reinstall
  /evolve-install --help       Show this help

PHASES:
  1. Python check       Verify Python >= 3.10 is available
  2. Environment setup  Create venv (if --local or auto) and install claude-evolve
  3. Claude CLI check   Verify `claude` is on PATH and authenticated
  4. MCP verification   Confirm claude-evolve MCP server registers and exposes tools
  5. Smoke test         Run a trivial claude call to confirm the bridge works

NEXT STEPS:
  After install completes, run `/evolve-interview` to define your first
  evolution task, or `/evolve` if you already have initial.py + evaluate.py.

Pre-Setup Check: Already Installed?

Before doing anything else, check if the plugin is already installed and working. Read the state file:

CLAUDE_EVOLVE_STATE="${CLAUDE_PLUGIN_ROOT:-.}/state/install-state.json"