Gitnexus Impact Analysis
abhigyanpatwari/gitnexusWhen you change a piece of code, other parts might break. This skill helps you find out what will be affected before you make any edits. It uses a tool called GitNexus to trace dependencies and show the danger zone.
You can ask questions like "Is it safe to change this function?" or "What will break if I modify this?" The skill answers with clear risk levels. Direct callers will break. Indirect ones are likely affected.
This makes your edits safer and saves you from surprises. It is useful before committing code or when planning a refactor. The analysis gives you confidence and control over your changes.
Add Gitnexus Impact Analysis skill to your workflow
Global
mkdir -p ~/.claude/skills/gitnexus-impact-analysisProject
mkdir -p .claude/skills/gitnexus-impact-analysisSource Repository
More Code Review & Quality Claude Code Skills
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