A read-only drift detector compares your code against the specification file SPEC.md. It finds places where the code has changed but the spec hasn't or vice versa. The results are grouped by severity so you can see what is most urgent.
The tool never writes anything. It only reports violations and gives hints for fixing them. You decide whether to fix the code or update the spec. This helps you catch drift early before it causes bigger problems.
Use it after each build and before each release. It checks invariants, interfaces, and task status. Each item is binary: it holds or it drifts. No scores, just clear findings.
Global
mkdir -p ~/.claude/skills/checkProject
mkdir -p .claude/skills/checkSource 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