OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add galaxy-dawn/claude-scholar --skill verification-loop
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.
npx skills add galaxy-dawn/claude-scholar --skill verification-loop
A comprehensive verification system for Claude Code sessions.
Invoke this skill:
Choose the commands adaptively for the current project instead of running every example blindly. Use the stack-appropriate command from references/STACK-DETECTION.md when the repo does not match the default examples below.
If build fails, STOP and fix before continuing.
Report all type errors. Fix critical ones before continuing.
Report:
Review each changed file for:
After running all phases, produce a verification report:
For long sessions, run verification every 15 minutes or after major changes:
This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.
Load only what is needed:
references/STACK-DETECTION.md - how to choose the right verification command set for the current reporeferences/REPORT-TEMPLATE.md - report structure for final verification outputexamples/example-verification-report.md - example final report# TypeScript projects
npx tsc --noEmit 2>&1 | head -30
# Python projects
pyright . 2>&1 | head -30# JavaScript/TypeScript
npm run lint 2>&1 | head -30
# Python
ruff check . 2>&1 | head -30# Python projects
pytest --cov=src --cov-report=term-missing 2>&1 | tail -50
# Node.js projects
npm run test -- --coverage 2>&1 | tail -50# Python: Check for secrets
grep -rn "sk-" --include="*.py" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.py" . 2>/dev/null | head -10
pip-audit
# Node.js: 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 debug statements
grep -rn "print(" --include="*.py" src/ 2>/dev/null | head -10
grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10# Show what changed
git diff --stat
git diff HEAD~1 --name-onlyVERIFICATION 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. ...Set a mental checkpoint:
- After completing each function
- After finishing a component
- Before moving to next task
Run: /verify