woz-bug
The woz-bug skill captures and submits bug reports for WOZCODE, triggering when users mention broken functionality or explicitly run the command. It extracts a one-line subject and full bug description from the user's message, securely pipes them to the backend via JSON, and automatically attaches session context including OS, architecture, and Node version without user intervention.
git clone --depth 1 https://github.com/WithWoz/wozcode-plugin /tmp/woz-bug && cp -r /tmp/woz-bug/skills/woz-bug ~/.claude/skills/woz-bugSKILL.md
# Report a WOZCODE bug
TRIGGER when: user says "report a bug", "woz is broken", "file a bug", or runs `/woz-bug`. For feature requests or general feedback, point them at `/woz-feedback` instead.
If the user already described the bug in their message, use it directly. If they invoked `/woz-bug` with no content (or said something too vague to act on), ask them: "What broke? What did you do, what happened, and what did you expect?" — then wait for their reply before submitting.
Derive `subject` (one-line headline, ~80 chars max) and `body` (the full message, verbatim) from the user's words. Don't paraphrase or add boilerplate.
Submit by piping a JSON envelope to stdin. Use a single-quoted heredoc (`<<'WOZ_FEEDBACK'`) so the shell does NO expansion — user text like `$(cmd)` or backticks is passed through literally and cannot execute. JSON-encode `subject` and `body` so embedded `"`, `\\`, or newlines survive:
```bash
node --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.js feedback <<'WOZ_FEEDBACK'
{"type":"BUG","subject":"<json-escaped subject>","body":"<json-escaped body>"}
WOZ_FEEDBACK
```
The CLI auto-attaches `CLAUDE_CODE_SESSION_ID`, anonymous telemetry id (unless the user opted out via `WOZCODE_TELEMETRY_DISABLED=true`), OS release, architecture, and Node.js runtime version. The email is auto-filled from the logged-in account.
On exit 0: tell the user "✅ Bug report sent. Thanks." On non-zero: relay the error verbatim and mention `support@withwoz.com` as a fallback.WOZCODE free-plan fallback agent — active when the monthly free-plan cap is exhausted. Claude Code's built-in Read, Edit, Write, Grep, Glob, and NotebookEdit are available; WOZCODE MCP tools are disallowed until the cap resets or the user upgrades.
WozCode enhanced coding agent with smart search, batch editing, and SQL introspection. Use as the default main thread agent.
Fast read-only agent for file searches, symbol lookups, and codebase questions like "where is X defined?", "where is X called?", or "how does X flow through the system?". Prefer over shell-based exploration when answering would take 3+ Search/Sql calls. Cheaper model (haiku) so delegation pays for itself on any real scan.
Compare WOZCODE vs vanilla Claude Code on the user's codebase — real cost, turn, and time savings. TRIGGER on "compare woz", "how much does woz save", "benchmark woz", "woz vs claude", "show me savings", or /woz-benchmark.
Authenticate with the Woz service. Use when the user needs to log in or when authentication is required.
Clear stored Woz credentials and log out.
Semantically search past Claude Code sessions to recall commands, solutions, and context from prior conversations. TRIGGER on 'remember when', 'last time', 'we did this before', 'how did we', or /woz-recall.
Show WOZCODE savings report - calls saved, time saved, tokens saved, and lifetime totals.