chameleon-journey

Solid

Use when the user explicitly invokes /chameleon-journey to run the comprehensive real-world journey harness against the chameleon plugin

Code & Development 9 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
33
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /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...

Details

Author
crisnahine
Repository
crisnahine/chameleon
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

harness-audit

Audits a Claude Code setup end-to-end: what loads every session, what it costs, and whether the harness's own claims hold. Inventories the standing surfaces (CLAUDE.md chain, personal/project/plugin skills, MCP instruction blocks, agent rosters, hooks, settings at every scope), quantifies their per-session token cost, runs five checks (self-consistency, duplication across scopes, enforcement parity, scope discipline, and a provisional routing-effectiveness check for doc-fleet repos) and reads the CLAUDE.md chain as intent (code outranks the doc; no restated stack, deps, or layout). Output is a quantified triage that stays in-repo: findings at machine scope (anything under ~/.claude, user or enterprise settings, global plugins) are reported for the owner to action, never edited. Use to review, slim, or sanity-check a whole Claude Code setup (including 'why is my context so big' or 'what loads every session') after major harness changes (a new plugin fleet, a new machine, a model release) or when sessions feel

3 Updated today
claudialnathan
AI & Automation Listed

run

Run cladding's autonomous loop — iterate ready features, dispatch the developer + reviewer personas through the active host adapter, run L1 gates, halt on HUMAN_REQUIRED or transport failure. Use only when the user explicitly asks for autonomous progress; the loop will modify files. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

14 Updated 2 days ago
qwerfunch
Code & Development Solid

using-chameleon

Active when .chameleon/ profile directory exists. Explains hook-injected pattern context and violation feedback for TypeScript/JavaScript, Ruby, and Python as first-class languages — framework-agnostic by default (it learns your repo's own conventions), with deeper awareness where conventions are strong: Rails for Ruby, Django/DRF/Flask/FastAPI for Python, and Next.js/NestJS for TypeScript/JavaScript.

9 Updated today
crisnahine