woz

# /woz — WOZCODE utilities One skill, eight subcommands. The first word of the arguments selects the subcommand: | Subcommand | Purpose | |---|---| | `login` | Authenticate with the Woz service (browser, API key, or token) | | `logout` | Clear stored credentials and log out | | `status` | Show authentication and subscription status | | `settings` | Show or update WOZCODE plugin settings | | `update` | Update the WOZCODE plugin to the latest version | | `share` | Print the referral share message | | `review` | Deep multi-persona code review of the current branch (requires KnowledgeBase access) | | `benchmark` | Side-by-side WOZCODE vs vanilla Claude Code comparison on the user's repo | TRIGGER when: the user runs `/woz <subcommand>`, or says "log in to woz", "woz status", "woz settings", "configure woz", "toggle attribution", "update woz", "refer a friend", "deep review", "final check before pushing", "review my branch", "is this ready to ship", "compare woz", "how much does woz save", "benchmark woz", or similar. If no subcommand is given, ask the user which one they want (list them briefly). Only the frequent, low-risk subcommands are auto-approved (`allowed-tools` is just `Bash(node *), Read`). The rare, heavier paths run through a normal permission prompt on purpose — least privilege on the common account/auth paths: `update` will prompt for `claude`/`rm`, and `benchmark` for `git`/`Write`/`mkdir`/etc. Approve those when the user runs them. ## login Dispatch on the ...