When reviewing a pull request, you need to check if the code matches the approved plan. This skill reads a spec context file and compares it to the actual changes. It finds important mismatches like missing features or wrong behavior.
Only use this skill when a spec context file is available. It helps you catch big differences between what was planned and what was built. Small harmless changes are ignored. The results go into the review file so the team can see them.
This tool is a helpful addition to normal code review. It makes sure the final code follows the original requirements. No extra reports are created. Everything stays inside the review notes.
Global
mkdir -p ~/.claude/skills/check-impl-against-specProject
mkdir -p .claude/skills/check-impl-against-specSource 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