| name | change-impact-radar |
| description | Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review. |
| origin | FlowDeck |
Change Impact Radar
Predicts blast surface before the AI touches a single file. Activate this skill by providing the intended change description to the agent.
When to Activate
Activate before:
- Any multi-file refactor
- API contract changes
- Schema migrations
- Dependency upgrades
- Auth / security changes
Workflow
- Read
.codebase/ARCHITECTURE.md and .codebase/STACK.md for system context
- Read
.codebase/MEMORY.json to trace the module dependency graph
- From the change description, identify all directly affected files
- Walk the dependency graph outward from affected files (depth ≤ 3 hops)
- Identify test files that cover the affected modules
- Flag any database schema, API contracts, or config changes
- Produce the impact map report
Impact Map Report Format
## Change Impact Report
### Direct Impact (files you will edit)
| File | Type | Risk |
|------|------|------|
### Indirect Impact (dependents, ≤3 hops)
| File | Dependency Chain | Risk |
|------|-----------------|------|
### API Contracts at Risk
- [contract name]: [why at risk]
### Tests to Run / Update
- [test file]: covers [module]
### Database / Config paths
- [path]: [what changes]
### Volatility Warnings
- [file]: marked as [stability level]
### Verdict: LOW | MEDIUM | HIGH impact
Guidance
- If MEMORY.json does not exist, run
/fd-task — its init step builds the graph.
- If a file has no test coverage and is indirectly impacted, flag it as "coverage gap".
- Never proceed with a HIGH impact change without human confirmation.
