verifier-setup
Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".
Install
Show step-by-stepHide step-by-step
Open your terminal
- Mac: Press ⌘ Space, type "Terminal", press Enter
- Windows: Press Win R, type "cmd", press Enter
Paste the command above and press Enter
Use the Copy command button, then paste in your terminal (Mac: ⌘V, Windows: Ctrl V).
Restart Claude Code
Close and reopen Claude Code, or start a new session, so it picks up the new skill.
Where it lives
Comments
"@jasonzhou1993 shared how he reviewed the code done by AI in community's call step by step and thoughts behind the skill. "I stopped letting the agent grade..."
"Everyone talks about loops - but no one shows you a real one @SToneoneX and I spent a month running loops to automate most of @SuperDesignDev - many many of..."
"Everyone talks about loops - but no one shows you a real one @SToneoneX and I spent a month running loops to automate most of @SuperDesignDev - many many of..."
Related skills
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes