dark-alex-17/coyote/verification-gates
Claude Code and agent skill by dark-alex-17/coyote
- community
Checking that the SKILL.md file is still in the repository.
Evidence requirements before claiming completion — diagnostics, build exit code, tests. No completion without proof. Grants shell access for running build/test commands.
Install
npx vskill@latest install dark-alex-17/coyote/verification-gatesSKILL.md
You are about to mark work complete. Before claiming "done," produce evidence. "I'm fairly confident it works" is not evidence.
Hard gates
A task is NOT complete until:
| Change kind | Required evidence | |
|---|---|---|
| File edit | Read the file to confirm the change landed; output is clean (or only pre-existing issues, explicitly noted) | |
| Build command exists | execute_command the build; exit code 0 | |
| Test command exists | execute_command the tests; pass (or explicit note of pre-existing failures unrelated to this change) | |
| Delegation | The delegate's result was received AND verified against your acceptance criteria |
No evidence = not complete. Marking a todo done without evidence is dishonest reporting.
The verification loop
After every meaningful edit:
- Read the changed file region (confirm the change actually landed where intended).
- If there's a project-level lint/typecheck command, run it on the touched files.
- Run the project's build/check command if one exists.
- Run the project's test command if one exists.
- Only then mark the corresponding todo
completed.
If any step fails: do not mark complete. Fix the issue or surface it explicitly.
Build/test detection (fallback)
If no build/test command is configured, try standard ones for the project:
- Rust:
cargo check,cargo test - Node/TS:
npm run build,npm test, orpnpm/yarnequivalents - Python:
pytest,python -m mypy <pkg>,ruff check - Go:
go build ./...,go test ./...
Run from the project root. Capture exit codes.
Distinguishing your failures from pre-existing failures
If build or tests fail, identify the cause:
- Caused by your change? → fix it before reporting complete.
- Pre-existing (unrelated)? → note it explicitly: "Done. Build passes. Note: 3 lint errors pre-existing in unrelated files, not touched."
Never silently leave broken state behind. Never delete a failing test to make CI green.
Anti-patterns (BLOCKING)
- "It should work" without running anything
- Marking a todo complete based on intent, not verified outcome
- Suppressing errors with
@ts-ignore,as any,#[allow(...)]on unfamiliar lints, empty catch blocks - Deleting failing tests to "pass"
- Reporting "all green" when you only ran a subset
Reporting completion
When the work is verifiably done, report in one sentence:
"Done. Build passes, 47 tests pass. Modifiedauth.rs:42-58to add JWT validation."
Not a paragraph. Not a victory lap. Specific, terse, evidence-backed.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingassets/skills/verification-gates/SKILL.md
Popularity
- Repository stars
- 57
- Repository forks
- 2
- 7-day trend score
- 20
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/dark-alex-17/coyote/verification-gates)