When you review a pull request, you want to know which parts of your code might be affected. This tool looks at the changes and uses a knowledge graph to find connected files, functions, and services.
The graph stores information about each part of your project. It includes nodes for files and classes and edges for how they connect. By matching changed files to nodes, the tool discovers what else depends on them.
You get a clear report with changed components, affected components, and a risk assessment. This helps you focus your review on the most important areas and avoid breaking something by accident.
Global
mkdir -p ~/.claude/skills/understand-diffProject
mkdir -p .claude/skills/understand-diffSource 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