kitty:impact

You can compute transitive dependents and upstream constraints by indexing the codebase and evaluating annotation coverage. This generates a structured subgraph context showing callers, callees, imports, and inheritance relationships to guide safe refactors, renames, or deletions.

Dependency graph impact analysis is used to answer what depends on a specific symbol and what breaks if that symbol changes. It surfaces structural hotspots via ranking and health checks to prioritize testing and verification during codebase modifications.

Yes, you can generate a structured subgraph context for orchestrated agent workflows when planning renames, refactors, or deletions. This context maps the complete dependency chain to guide downstream agents in executing safe codebase modifications.

Yes, indexing the codebase is required before running impact analysis. The indexing process maps the dependency chains and evaluates annotation coverage, which is necessary to assemble the accurate subgraph context for downstream agent orchestration.

The best way to assess structural risk for code deletions is to surface hotspots via ranking and structural health checks. This impact analysis identifies high-risk dependency chains and upstream constraints, allowing you to prioritize testing exactly where changes ripple.