Scope Analysis

Name: Scope Analysis
Availability: InStock
Author: strategicmilk

Generate a JSON scope report of direct and transitive code change impacts.

Updated Mar 3, 2026

Search Tags:#analysis #lsp #scope #dependency-mapping #risk #impact-assessment

Ready to run

npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill scope-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Scope Analysis
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/foreman/scope-analysis
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill scope-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning code changes without knowing their full blast radius often leads to broken builds, missed tests, and costly rollbacks. This skill automatically maps every affected file, test, and dependency before any implementation begins.

Core Features & Use Cases

Dependency Mapping: Traverses LSP references and import graphs to locate direct and transitive impacts.
Test Coverage Insight: Identifies which tests are affected and highlights uncovered code paths.
Risk Classification: Categorizes changes as Trivial, Scoped, or Complex with actionable recommendations.
Use Cases: Renaming enums, modifying public APIs, refactoring shared modules, or any change that could ripple through the codebase.

Quick Start

Ask the foreman to perform a scope analysis for renaming AgentType.BUILDER to AgentType.WORKER.

Frequently Asked Questions about Scope Analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map the blast radius of a code change before implementation?▼

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.

What is dependency mapping for code refactoring?▼

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.

How do I identify affected tests when modifying public APIs?▼

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.

Can I use LSP references for risk classification of shared module refactoring?▼

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.

Does scope analysis work for multi-agent LLM orchestration systems?▼

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.

What are the limitations of using import graphs for transitive impact assessment?▼

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.