| name | verification-loop |
| description | Use when implementing, fixing, refactoring, or reviewing code and you need a disciplined verification loop with builds, tests, type checks, linting, formatting, or manual checks. |
Verification Loop
Use this skill to turn "done" into something observable.
Workflow
- Define the expected behavior in one sentence.
- Identify the smallest meaningful checks for the change.
- Run the cheapest checks first, then broader checks if risk is higher.
- If a check fails, fix the cause and rerun the relevant check.
- Report what passed, what was skipped, and any remaining risk.
Check Selection
Prefer existing project commands. Look for package.json, Makefile, pyproject.toml, go.mod, pom.xml, build.gradle, CI config, or repo docs.
Use these as defaults when present:
- TypeScript/JavaScript: typecheck, lint, unit tests, targeted Playwright tests for UI.
- Python: unit tests, type checks if configured, formatter or linter if configured.
- Go:
go test ./....
- Java/Kotlin: project build and targeted tests.
- Docs/config only: parse or render the touched file format when possible.
Output
End with:
- Checks run.
- Result of each check.
- Checks not run and why.
- Residual risk if any.