woz-benchmark

# WOZCODE Savings Benchmark Run a side-by-side comparison of WOZCODE vs vanilla Claude Code on the user's own codebase. Each prompt runs twice against a fresh copy of the repo with `git reset --hard` between runs, so the target MUST be a clean git repo. TRIGGER: "compare woz", "how much does woz save", "benchmark woz", "woz vs claude", "show me the savings", "is woz worth it", or `/woz-benchmark`. ## Prerequisites - User logged in to WOZCODE. - Target directory is a git repo with a clean working tree. ## Steps ### 1. Gather inputs — BE BRIEF Ask for all three in ONE short message (< 10 lines). Do not re-explain what the benchmark does — the user already invoked it. 1. **Target directory** — absolute path to a clean git repo to run the test on. 2. **Prompts** — 2–10 real coding tasks. Tell them briefly: "meaty feature/refactor/bugfix work, not one-liners — trivial prompts hide WOZCODE's advantage". If they don't have prompts in mind, offer to suggest some after looking at their repo. 3. **Environment setup** (optional) — one line: "Anything Claude needs already in place (DB seeded, services running, credentials in `.env`)? Skip if the repo is self-contained." Do NOT ask about the model. Default to `opus` in the YAML config. Only switch to `sonnet` or `haiku` if the user volunteers a different choice in their answer. ### 2. Validate the target Before writing any config, verify the target is usable: ```bash test -d <target> git -C <target> rev-parse --git-dir git -C ...