verification-loop
Antigravity-inspired verification loop that ensures code passes all quality gates before being presented as complete.
When & Why to Use This Skill
This Claude skill implements a rigorous, Antigravity-inspired verification loop that automates code quality checks. It ensures all AI-generated code passes through static analysis, formatting, unit testing, and build processes before being finalized, significantly reducing bugs and ensuring production-ready output.
Use Cases
- Automated Quality Assurance: Ensuring new features or components meet all project-specific linting and formatting standards before they are presented to the user.
- Reliable Bug Fixing: Verifying that patches resolve the root cause and pass all regression tests without introducing new errors into the codebase.
- Safe Refactoring: Maintaining code integrity during structural changes by continuously running analysis and test loops to catch regressions early.
- Pre-deployment Validation: Confirming that code compiles and builds successfully across different environments (e.g., Flutter, React, Python, Node.js) to prevent CI/CD pipeline failures.
| name | verification-loop |
|---|---|
| description | Antigravity-inspired verification loop that ensures code passes all quality gates before being presented as complete. |
Verification Loop Skill
Ensures code meets quality standards before presenting as complete.
Purpose
Implement a verification loop where the agent iterates until all quality gates pass, inspired by Google Antigravity's verification-first philosophy.
The Loop
┌─────────────────────────────────────────────────────────────────┐
│ VERIFICATION LOOP │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. WRITE CODE │
│ ↓ │
│ 2. RUN ANALYSIS ──────────────→ Issues? → Fix → Loop │
│ ↓ Clean │
│ 3. RUN FORMATTER ─────────────→ Changed? → Commit → Continue │
│ ↓ Consistent │
│ 4. RUN TESTS ─────────────────→ Failed? → Fix → Loop │
│ ↓ Passing │
│ 5. RUN BUILD ─────────────────→ Error? → Fix → Loop │
│ ↓ Compiles │
│ 6. PRESENT AS COMPLETE │
│ │
└─────────────────────────────────────────────────────────────────┘
Stack-Specific Commands
Flutter/Dart
flutter analyze --fatal-infos --fatal-warnings
dart format --set-exit-if-changed .
flutter test
flutter build web
React/TypeScript
npm run lint
npm run typecheck
npm test
npm run build
Python
ruff check .
mypy src/
pytest
ruff format --check .
Node.js
npm run lint
npm run typecheck
npm test
npm run build
Loop Rules
- Maximum 3 iterations before asking user for help
- Fix root cause, not symptoms
- If tests fail for unrelated code: note in artifact, don't block
- Never present incomplete work as done
Verification Levels
| Scenario | Verification Level |
|---|---|
| New component/module | Full loop (all steps) |
| Bug fix | Analysis + Tests + Build |
| Refactoring | Analysis + Tests |
| Documentation only | Skip verification |
| Config change | Build only |
Verification Artifact
When completing a task, generate this artifact:
## Verification Report
| Check | Status | Details |
|-------|--------|---------|
| Analysis | ✅ Pass | 0 warnings, 0 errors |
| Format | ✅ Pass | No changes needed |
| Tests | ✅ Pass | X/Y tests passing |
| Build | ✅ Pass | Compiled successfully |
### Files Modified
- `path/to/file1.ts`
- `path/to/file2.ts`
### Notes
{Any relevant observations}
Usage
Automatic
The verification loop should run automatically when the frontend-developer, react-developer, flutter-developer, python-developer, or node-developer agent completes code changes.
Manual Trigger
/verify
Integration with Subagents
Add to relevant developer agents:
## Verification Protocol
After writing code, ALWAYS run the verification loop:
1. Run static analysis - Fix ALL warnings, not just errors
2. Check formatting - Ensure consistent style
3. Run tests - All tests must pass
4. Run build - Confirm it compiles
Do NOT present code as complete until all steps pass.
If a step fails:
- Read the error message
- Fix the issue
- Re-run from step 1
- Maximum 3 iterations before asking user for help
Benefits
- Higher Quality: Code is verified before user sees it
- Faster Iteration: Issues caught immediately
- Trust: "Complete" means actually complete
- Audit Trail: Verification artifacts document quality
Anti-Patterns
| Don't | Do Instead |
|---|---|
| Skip analysis because "it's just a warning" | Treat warnings as errors |
| Ignore failing tests for unrelated code | Fix or document with explanation |
| Present code without building | Always confirm it compiles |
| Run verification once | Loop until clean |