Scope Analysis

To map the blast radius of a code change, you can traverse LSP references and import graphs to identify direct and transitive impacts. This generates a scope report detailing affected files, tests, and dependencies to prevent broken builds.

Dependency mapping for code refactoring is the process of traversing import graphs to locate every direct and transitive impact of a proposed change. It categorizes modifications as Trivial, Scoped, or Complex to guide task decomposition and highlight test coverage gaps.

To identify affected tests when modifying public APIs, analyze the codebase scope to highlight uncovered paths and map test coverage gaps. This process generates a JSON scope report that details exactly which tests are impacted by the API changes.

Yes, you can use LSP references to perform risk classification for shared module refactoring. The analysis categorizes changes as Trivial, Scoped, or Complex by mapping the full blast radius across files and dependencies, providing actionable recommendations.

Yes, scope analysis is explicitly designed to apply to multi-agent LLM orchestration systems. It maps the blast radius of changes to public APIs, enums, or shared modules within these architectures, outputting a JSON report to guide task decomposition.

Using import graphs for transitive impact assessment relies on accurately traversing LSP references, meaning limitations arise if references are dynamically resolved or missing. The resulting JSON scope report can only classify risks and highlight coverage gaps based on statically mapped dependencies.