woz-feedback
starsforks
How to install woz-feedback?
withwoz/wozcode-plugin/woz-feedback
$npx -y skills add WithWoz/wozcode-plugin --skill woz-feedbackSend feedback or a bug report to the WOZCODE team. Bug reports are tagged for triage and auto-attach session context (session id, anonymous id, OS, arch, Node version).
SKILL.md
| 1 | # WOZCODE feedback & bug reports |
| 2 | |
| 3 | TRIGGER when: user says "send feedback", "share feedback", "i wish woz", "feature request", "report a bug", "woz is broken", "file a bug", or runs `/woz-feedback`. |
| 4 | |
| 5 | Decide the type from the user's words: broken behavior is a **bug**; feature requests and general thoughts are **feedback**. |
| 6 | |
| 7 | If the user already described their feedback or bug in their message, use it directly. If they invoked `/woz-feedback` with no content (or said something too vague to act on), ask them — for feedback: "What would you like to share with the WOZCODE team?"; for a bug: "What broke? What did you do, what happened, and what did you expect?" — then wait for their reply before submitting. |
| 8 | |
| 9 | 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. |
| 10 | |
| 11 | 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. |
| 12 | |
| 13 | For general feedback (feature requests, thoughts) — this is the default, omit `type`: |
| 14 | |
| 15 | ```bash |
| 16 | node --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.js feedback <<'WOZ_FEEDBACK' |
| 17 | {"subject":"<json-escaped subject>","body":"<json-escaped body>"} |
| 18 | WOZ_FEEDBACK |
| 19 | ``` |
| 20 | |
| 21 | For a bug report, add `"type":"BUG"` so it routes to bug triage: |
| 22 | |
| 23 | ```bash |
| 24 | node --no-warnings=ExperimentalWarning ${CLAUDE_PLUGIN_ROOT}/scripts/wozcode-cli.js feedback <<'WOZ_FEEDBACK' |
| 25 | {"type":"BUG","subject":"<json-escaped subject>","body":"<json-escaped body>"} |
| 26 | WOZ_FEEDBACK |
| 27 | ``` |
| 28 | |
| 29 | 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. |
| 30 | |
| 31 | On exit 0: tell the user "✅ Sent. Thanks." On non-zero: relay the error verbatim and mention `support@withwoz.com` as a fallback. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
