Verifier Setup
Set a repo up to prove engineering-task work actually works before it ships.
Install
npx skills add AI-Builder-Club/skills --skill verifier-setup -g -a claude-code -y- Repository
- AI-Builder-Club/skills1.3k
- Category
- Testing
- Updated
- 2mo ago
- License
- See repository
- Context cost
- Mediumabout 1,892 tokens
- Runs scripts
- No, instructions only
What it does
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".
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:
- A
/verifyskill,.claude/skills/verify/SKILL.md, the repo-tailored per-task verification SOP (spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded). Generated in Step 5. - A
/dev-localskill + its script,scripts/dev-local.shand.claude/skills/dev-local/SKILL.md, viadev-local-setup(Step 2) if not already present. The one-command stack/verifydepends on. - The driver skill installed, the
playwright-cliskill for web apps (Step 2); for non-web, the concrete exercise tool confirmed present.
Step 0, Inventory what already exists (check before you add ANYTHING)
Before creating anything, take stock, the repo may already have some of this, under whatever name or layout its team chose. Look for the capability, not a specific filename; the paths below are only examples. For each, decide reuse as-is / adapt-extend / create fresh, never blindly overwrite working setup:
