gitnexus-impact-analysis

Impact analysis identifies what will break by mapping git diffs to direct callers, transitive dependencies, and affected processes. It provides caller depth, confidence scores, and a summarized risk level to help plan changes or block unsafe commits before they happen.

Dependency analysis determines breakage by querying upstream and downstream dependencies to enumerate dependents by depth. It assigns confidence scores where depth one means will break, depth two means likely affected, and depth three means may need testing.

Pre-commit impact analysis requires repositories with gitnexus indexing and gitnexus:// process documents. This enables upstream and downstream dependency queries alongside git-diff based change mapping to identify affected execution flows.

You can map code changes to critical runtime processes by inspecting process documents via gitnexus. This correlates modified code symbols with runtime execution flows and critical paths like authentication or payments to assess change risk.

The best way to assess refactor risk is running impact queries to enumerate dependents by depth with confidence scores, then inspecting process documents. This identifies affected execution flows and generates an overall risk level for change planning.

Confidence scores indicate severity: depth one means will break, depth two means likely affected, and depth three means may need testing. These scores help prioritize mitigation efforts during pre-commit risk assessment.