skills
Skill2 starsChanged 5 months agoMITView on GitHub
A comprehensive verification system for Claude Code sessions. Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring If build fails, STOP and fix before continuing. Report all type errors. Fix critical ones before continuing. Report: - Total tests: X - Passed: X - Failed: X - Coverage: X% Review each changed file for: - Unintended changes - Missing error handling…
64 other projects use a version of this.
Adopted by
Most recently taken up by
- liweijie0812/tdesign-skillstheir own version, first seen Nov 8, 2026
- shuji-bonji/ai-agent-architecturetheir own version, first seen Nov 8, 2026
- etr/groundworktheir own version, first seen Nov 8, 2026
- jackccrawford/Geniuztheir own version, first seen Nov 4, 2026
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- Jopie64/skills-agent-skilltheir own version, first seen Nov 1, 2026
Other versions64 projects use a version of this.
Word for word · 6
- xfstudio/skills★ 9100% same
- Lukasbrujula/claude-code-framework★ 4100% same
- mstuder-slalom/everything-claude-code★ 1100% same
- zkw15555506767-boop/claude-skills★ 1100% same
- EvanZzhang/claude-configs★ 0100% same
- HABUBUSS/everything-claude-code★ 0100% same
Edited · 0
None found.
Wrote their own version · 58
- GoogleCloudPlatform/training-data-analyst★ 8.7ksame name
- flexprice/flexprice★ 6.9ksame name
- BerriAI/litellm-agent-platform★ 1.3ksame name
- LiteLLM-Labs/litellm-agent-control-plane★ 1.3ksame name
- ahmadawais/ramadan-cli★ 601same name
- caipe-io/ai-platform-engineering★ 438same name
- cnoe-io/ai-platform-engineering★ 438same name
- kagenti/kagenti★ 303same name
- GoBetterAuth/go-better-auth★ 277same name
- second-state/qwen3_asr_rs★ 253same name
48 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- skills/AGENTS.mdAGENTS.md
- my-config/CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- xiaolai-methodologySkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After completing a feature or significant code change
- Distinctive: line 9
Before creating a PR
- Distinctive: line 10
When you want to ensure quality gates pass
- Distinctive: line 23
If build fails, STOP and fix before continuing.
- Distinctive: line 84
After running all phases, produce a verification report:
“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verification Loop Skill
A comprehensive verification system for Claude Code sessions.
When to Use
Invoke this skill:
- After completing a feature or significant code change
- Before creating a PR
- When you want to ensure quality gates pass
- After refactoring
Verification Phases
Phase 1: Build Verification
# Check if project builds
npm run build 2>&1 | tail -20
# OR
pnpm build 2>&1 | tail -20If build fails, STOP and fix before continuing.
Phase 2: Type Check
# TypeScript projects
npx tsc --noEmit 2>&1 | head -30
# Python projects
pyright . 2>&1 | head -30Report all type errors. Fix critical ones before continuing.
Phase 3: Lint Check
# JavaScript/TypeScript
npm run lint 2>&1 | head -30
# Python
ruff check . 2>&1 | head -30Phase 4: Test Suite
# Run tests with coverage
npm run test -- --coverage 2>&1 | tail -50
# Check coverage threshold
# Target: 80% minimumReport:
- Total tests: X
- Passed: X
- Failed: X
- Coverage: X%
Phase 5: Security Scan
# 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" src/ 2>/dev/null | head -10Phase 6: Diff Review
# Show what changed
git diff --stat
git diff HEAD~1 --name-onlyReview each changed file for:
- Unintended changes
- Missing error handling
- Potential edge cases
Output Format
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. ...Continuous Mode
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: /verifyIntegration with Hooks
This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

