A verification loop runs a set of checks after each code change. It helps developers catch problems early. The process includes build, type check, lint, tests, security scan, and diff review.
You can use this loop after finishing a feature or before creating a pull request. Each phase is run with simple commands. If any phase fails, you stop and fix the issue first.
The final report shows pass or fail for every check. It tells you if your code is ready for a pull request. This keeps your work clean and safe.
Global
mkdir -p ~/.claude/skills/verification-loopProject
mkdir -p .claude/skills/verification-loopSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective