Impact Analysis

get_impact

Blast-radius analysis via reverse-BFS. Answers “what breaks if I change X?” across code, infrastructure, APIs, and documentation.

Results are grouped by depth:

direct (depth 1, confidence 1.0)
indirect (depth 2, confidence 0.6)
peripheral (depth 3+, confidence 0.3)

Also returns implementor_impact (types implementing the root interface) and cross_domain_impact covering DEPLOYS, CONSUMES, CONFIGURED_BY, DOCUMENTS, and MENTIONS edges.

Parameters

Parameter	Type	Required	Description
`symbol`	string	Conditional	Entity name to analyse (e.g. `CarveEgoGraph`). Required unless `files` is provided.
`files`	string	Conditional	Comma-separated file paths for change-set impact (PR blast radius). Aggregates impact across all entities in the specified files. Alternative to `symbol`.
`depth`	number	No	Max hop depth. Default 3, max 10.
`token_budget`	number	No	Max response size in tokens (default 2000). Peripheral nodes dropped first, then indirect. Direct callers always kept.
`projects`	string	No	Comma-separated federation aliases to check sibling project dependents.
`scope`	string	No	`review`: enriched output for code review. Adds blast_radius summary, test_gaps, risk_flags, and failure_history. Default: standard analysis.

Example: Single Entity

{
  "tool": "get_impact",
  "arguments": {
    "symbol": "CarveEgoGraph",
    "depth": 3
  }
}

Example: PR Blast Radius

{
  "tool": "get_impact",
  "arguments": {
    "files": "internal/graph/carve.go,internal/graph/ppr.go",
    "scope": "review"
  }
}

Review Scope

When scope="review", the response includes additional fields:

blast_radius — summary with direct/transitive/files/untested/high-risk counts
test_gaps — impacted entities with zero test coverage
risk_flags — entities with negative quality scores from historical signals
failure_history — recent failure episodes related to the entity