impact-analysislisted
Install: claude install-skill ShiftinBits/constellation-claude
# Impact Analysis
Use the `code_intel` tool to assess the impact of proposed code changes before they happen, identifying affected files, dependents, public API exposure, and risk level.
## When to Run
Run an impact analysis when **any** of the following apply:
- About to rename, move, delete, or significantly modify a code symbol
- About to change a function signature, class shape, or exported interface
- Considering removing code suspected to be dead
- Planning a multi-file refactor and need a safe order
- User asks "what uses X?", "what would break?", "is X safe to remove?"
If the change is purely additive (new file, new function, no signature changes to existing exports), impact analysis is usually unnecessary — skip it.
## How to Run
Call the `code_intel` tool with this code:
```javascript
const result = await api.impactAnalysis({
symbolName: "TargetSymbol",
filePath: "src/path/to/file.ts", // optional, helps disambiguate
depth: 3
});
return result;
```
For broader context (large refactors, whole-file changes), pair with dependency mapping:
```javascript
const [impact, deps, dependents] = await Promise.all([
api.impactAnalysis({ symbolName, filePath, depth: 3 }),
api.getDependencies({ filePath, depth: 2 }),
api.getDependents({ filePath, depth: 2 }),
]);
return { impact, deps, dependents };
```
For confirming dead code:
```javascript
const usage = await api.traceSymbolUsage({ symbolName, filePath });
return usage;
```
## Interpreting Results
The `impac