gitnexus-impact-analysis

Code impact analysis detects dependencies and potential issues before code modification. You can query specific targets and directions to understand the potential blast radius of changing a particular code segment safely.

Dependency risk assessment evaluates the risk level of code changes using a depth and confidence scale. It works for pre-commit checks by identifying what will break if you change a particular code segment before committing.

Yes, you need access to GitNexus to assess the blast radius of code changes. The Skill requires GitNexus to perform dependency detection and safety analysis during your pre-commit review process.

You can check upstream dependencies by running an impact query with target and direction parameters. For example, querying 'validateUser' with the 'upstream' direction identifies what depends on that specific function.

Confidence and depth parameters scale the risk assessment of code changes, but the analysis is limited to detecting dependencies and potential issues. It guides pre-commit checks but does not automatically resolve the detected code conflicts.

The best way to avoid breaking a codebase is performing safety analysis before editing. Assessing code changes identifies dependent components and evaluates risk levels, preventing breaking modifications from being committed.