verification-loops
Verify changes work before completing. Use browser testing, test suites, and manual checks.
When & Why to Use This Skill
The Verification Loops skill is designed to ensure code integrity and functional correctness by implementing a systematic validation workflow. It automates the process of running test suites, performing browser-based UI testing via Playwright, and executing build and lint checks, ensuring that every modification is thoroughly vetted before being marked as complete.
Use Cases
- Automated Regression Testing: Automatically trigger test suites like npm test, pytest, or cargo test after code modifications to prevent regressions.
- End-to-End UI Verification: Use Playwright integration to navigate web pages, inspect accessibility trees, and capture screenshots for visual validation of frontend changes.
- Pre-Commit Quality Assurance: Run build scripts and linting tools (e.g., ruff, golangci-lint) to catch syntax errors and maintain code style consistency before deployment.
- Continuous Integration Support: Act as a local quality gate to ensure that code meets all project requirements and passes a comprehensive checklist before being pushed to a repository.
| name | verification-loops |
|---|---|
| description | Verify changes work before completing. Use browser testing, test suites, and manual checks. |
| triggers | testing, verification, QA, quality assurance, checking changes, validating code, build check, lint check |
Verification Loops
Always verify changes work before marking tasks complete.
Verification Methods
1. Test Suite
npm test / pytest / cargo test / go test ./...
2. Browser (Playwright MCP)
browser_navigate- Go to pagebrowser_snapshot- Accessibility treebrowser_take_screenshot- Visual verification
3. Build Verification
npm run build / cargo build / go build ./...
4. Lint Check
npm run lint / ruff check . / golangci-lint run
Checklist Before Completing
- Tests pass
- Build succeeds
- Lint passes
- Manual verification (if UI)