verifier-setup
把验证流程模板化，确保每项变更可在本地或沙箱被证明可运行。
可能安装驱动或触发网络操作，需注意外部依赖
为仓库搭建能在提交前证明工程任务可行的 /verify 验证脚手架。
为仓库搭建能在提交前证明工程工作可行的 /verify 验证脚手架：会确认或生成一键启动的 dev-local、问你是本地跑还是在沙箱(crabbox) 执行、并安装驱动（默认是 Playwright/playwright-cli）。最终产物有提交的 /verify 模板、/dev-local 脚本和驱动，方便后续为每个任务跑出可复现的验证证据（截图/视频并开 PR）。
▸ 展开 SKILL.md 英文原文
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".
帮我安装这个 skill：https://raw.githubusercontent.com/AI-Builder-Club/skills/main/skills/verifier-setup/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/AI-Builder-Club/skills/main/skills/verifier-setup/SKILL.md"# verifier-setup — scaffold this repo's `/verify` skill Goal: leave the repo able to *prove an engineering task works before it ships* — run once, and it wires up everything the per-task `/verify` loop needs. You are **setting up** — not verifying anything yourself right now. The `/verify` template lives at `assets/verify.template.md` (next to this skill). Parallels `dev-local-setup` (which generates a script + its skill doc): a setup skill that leaves behind reusable, repo-specific artifacts. ## What this produces (the outputs) Running `verifier-setup` end-to-end leaves the repo with: 1. **A `/verify` skill** — `.claude/skills/verify/SKILL.md`, the repo-tailored per-task verification