What problem does it solve?
When changing a port interface, small edits can cascade across implementations, use cases, presentation layers, and tests causing widespread breakage and missed updates; this Skill uncovers the full blast radius before any code is changed so you can plan a minimal, safe rollout.
Core Features & Use Cases
- Locate interface definitions: Find the canonical interface source inside the application ports directory and record its file and symbol path.
- Discover implementors and consumers: Identify infrastructure implementations, injected use cases, and presentation code that depend on the interface.
- Assess transitive impact and tests: Use a code-review graph to reveal transitive dependencies and enumerate affected unit and integration tests to produce a prioritized change checklist.
- Use Case: Preparing to add or change a method on an output port interface and needing an exact list of files and tests to update beforehand.
Quick Start
Ask Serena to analyze the interface IFeatureRepository at packages/core/src/application/ports/output/repositories/feature-repository.interface.ts and generate a layer-by-layer impact checklist listing implementors, consuming use cases, presentation references, and affected tests.