← 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 · ★ 9 · Code & Development · score 74
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. **Requires a development clone of the chameleon repository.** The installed plugin ships only the runtime surface (`hooks/`, `skills/`, `mcp/`, ...); it does not include `tests/`. Every command below runs from the root of the CLONE, not from the installed plugin directory. ## Defaults Full run: 21 acts, ~$38 cost ceiling, ~65 min runtime, $40 hard budget cap (default `--max-budget-usd`). ## Confirm the spend first A full run bills real API usage and takes about an hour, so it is not something to start on the user's behalf from a bare `/chameleon-journey`. Before the first Claude-spawning command: 1. Run `--dry-run` (free) to confirm the preflight passes, and `--list` if the user wants to see what would execute. 2. State the projected cost, the runtime, and the budget cap that will apply. 3. **Ask the user to confirm, and wait for an affirmative answer.** Typing the slash command is a request to use the harness, not standing approval to spend ~$38. Skip the confirmation only when the user's own message already authorized the spend (an explicit "yes, run the full journey" or a `--max-budget-usd` they chose themselves). A run gated to zero spend (`--dry-run`, `--list`) needs no confirmation. ## Run Only after the user has confirmed. From the chameleon repo (clone) root: ```bas