Agent skill · pskoett
verify-gate
Runs project compile, test, and lint commands between implementation and quality review. Gates simplify-and-harden behind machine verification. If checks fail, routes back to implementation with diagnostics for a fix loop. If checks pass, signals ready for the quality pass. Use after any implementation work completes and before simplify-and-harden. Essential for the inner loop's verify step.
What it needs
About 6k tokens when loaded.
What this skill does
Verify Gate Machine verification gate between implementation and quality review. Runs the project's compile, test, and lint commands. If any fail, enters a fix loop. If all pass, unblocks simplify-and-harden. This is the inner loop's verify step. Without it, the agent hands off code with zero machine signal about whether it actually works. When to Use After any implementation work completes, before signaling "done" Before running simplify-and-harden After fixing findings from an independent simplify, harden, spec, or code review Any time you want a machine-verified green signal Pipeline Position Step 1: Discover Project Commands Read the project's configuration to find verification commands. Check these sources in order: 1. Project instruction files (CLAUDE.md, AGENTS.md, .github/copilot-instructions.md) — look for a ## Verification or ## Test Commands section 2. package.json — scripts.test, scripts.lint, scripts.typecheck, scripts.build. Also check for a bun.lock / bun.lockb alongside it → prefer bun run <script> over npm run <script> when present. Check for pnpm-lock.yaml → prefer pnpm run. Check for yarn.lock → prefer yarn. 3. Makefile / Justfile — test, lint, check, build targets 4. Cargo.toml — cargo build, cargo test, cargo clippy 5. pyproject.toml / setup.cfg — pytest, mypy, ruff 6. go.mod — go build ./..., go test ./..., go vet ./... 7. deno.json / deno.jsonc — deno task <name> for any defined tasks If no commands are discoverable, ask the user once and suggest they add a ## Verification section to their project instruction files (CLAUDE.md, AGENTS.md, or equivalent) for future sessions: Define acceptance evidence Before running commands, translate each user acceptance criterion into observable evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pskoett/verify-gate--8791ff