← ClaudeAtlas

chameleon-journeylisted

Use when the user explicitly invokes /chameleon-journey to run the comprehensive real-world journey harness against the chameleon plugin
crisnahine/chameleon · ★ 2 · AI & Automation · score 73
Install: claude install-skill crisnahine/chameleon
# /chameleon-journey Run the journey harness at `tests/journey/`. The harness verifies chameleon's full lifecycle by spawning real `claude -p` subprocesses against committed seed fixtures. ## Defaults Full run: 18 acts, ~$33 cost ceiling, ~65 min runtime, $35 hard budget cap (default `--max-budget-usd`). ## Run From the chameleon repo root: ```bash mcp/.venv/bin/python -m tests.journey.runner ``` Variations: - `--list`: show acts + phase coverage, exit 0. - `--dry-run`: run preflight only (claude on PATH, git >= 2.28, fixtures present, mcp/.venv), exit before any Claude spawn. - `--max-budget-usd N`: pre-flight + mid-run abort if projected cost exceeds N (default 35). - `--results-dir DIR`: override per-run output dir (default `tests/journey/results/`). ## Output - stderr: per-act `[ACT N] ...` markers + cost + duration. - `tests/journey/results/journey_<ts>/run.json` + `run.md`: per-act + per-phase results. - `tests/journey/results/journey_<ts>/checkpoints/<act>.jsonl`: per-act checkpoint data for post-mortem. ## Notes The full run requires: - `claude` CLI on PATH with API access. - git >= 2.28 (for `git init --initial-branch=main`). - `mcp/.venv/bin/python` (run `cd mcp && uv sync` if missing). The harness writes ALL state to a per-run dir; the developer's own `~/.local/share/chameleon/` is never touched.