verifier-setup

Solid

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".

Code & Development 1,064 stars 141 forks Updated today

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
0
Description 5%
100

Skill Content

# 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 SOP (spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded). Generated in Step 5. 2. **A `/dev-local` skill + its script** — `scripts/dev-local.sh` **and** `.claude/skills/dev-local/SKILL.md`, via `dev-local-setup` (Step 2) if not already present. The one-command stack `/verify` depends on. 3. **The driver skill installed** — the `playwright-cli` skill 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, de...

Details

Author
AI-Builder-Club
Repository
AI-Builder-Club/skills
Created
1 months ago
Last Updated
today
Language
Python
License
None

Integrates with

Playwright · Testing

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

verify

Check that a change actually works — run the project's tests, then drive the real thing (the command, the page, the function) and confirm the effect. Reports a clear verdict, and says honestly what could not be checked and why, instead of quietly skipping it.

0 Updated today
grinchenkoedu
AI & Automation Listed

role-verify

Install verify role on a session. The fast independent check that a claimed artifact is actually done — spawned proactively before any parent reports done, opens a PR, deploys, or publishes.

2 Updated 1 weeks ago
ryan-scheinberg
Code & Development Listed

verify

Run tests, linting, and type checking with structured evidence collection. Auto-detects project stack (Node, Python, Rust). Reports quality level: all clear, warnings, failures, or blocked. Optional streak gate requires N consecutive green runs before declaring success. Use when: validating code before commit, checking CI readiness, running all project checks, or collecting evidence for a PR. Triggers on: verify, run checks, quality check, run tests, does it pass, lint, typecheck, pre-commit check, green, validate, flaky test, streak gate

6 Updated today
ArieGoldkin