A comprehensive verification system for Claude Code sessions.
50
55%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/verification-loop/SKILL.mdA comprehensive verification system for Claude Code sessions.
Invoke this skill:
npx nx run-many --target=build --all --parallel 2>&1 | tail -20If build fails, STOP and fix before continuing.
npx tsc --noEmit 2>&1 | head -30Report all type errors. Fix critical ones before continuing.
npx nx lint meerkat-core 2>&1 | head -30# Run tests for affected project(s)
npx nx test meerkat-core 2>&1 | tail -50
# Run all tests
npx nx run-many --target=test --all 2>&1 | tail -50
# Target: 80% minimum coverageReport:
# Check for secrets
grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
# Check for console.log
grep -rn "console.log" --include="*.ts" --include="*.tsx" packages/ 2>/dev/null | head -10git diff --stat
git diff HEAD~1 --name-onlyReview each changed file for:
. delimiters, empty arrays)After running all phases, produce a verification report:
VERIFICATION REPORT
==================
Build: [PASS/FAIL]
Types: [PASS/FAIL] (X errors)
Lint: [PASS/FAIL] (X warnings)
Tests: [PASS/FAIL] (X/Y passed, Z% coverage)
Security: [PASS/FAIL] (X issues)
Diff: [X files changed]
Overall: [READY/NOT READY] for PR
Issues to Fix:
1. ...
2. ...For long sessions, run verification every 15 minutes or after major changes:
Set a mental checkpoint:
- After completing each function
- After finishing a component
- Before moving to next task
Run: /verifyBefore ANY git push, run the full monorepo test suite:
npx nx run-many --target=test --all 2>&1 | tail -50Rules:
This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.
47baa4e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.