What problem does it solve?
This Skill helps you analyze software systems as graphs so you can spot structural risk before it causes outages, slow delivery, or large change cascades. It is especially useful when a dependency network feels fragile, tightly coupled, or hard to reason about from local code inspection alone.
Core Features & Use Cases
- Graph-Structured Diagnosis: Reviews systems through nodes, edges, direction, and centrality to identify hubs, bottlenecks, and risky dependency concentration.
- Failure and Blast Radius Analysis: Finds articulation points, bridges, cycles, and strongly connected components to estimate how outages or breaking changes propagate.
- Architecture and Refactoring Guidance: Recommends targeted structural changes for service graphs, module imports, event systems, IAM relationships, build dependencies, and ownership networks.
- Use Case: When one shared library, gateway service, or platform component seems to affect many teams, this Skill helps determine whether it is a safe keystone or a dangerous single point of failure.
Quick Start
Ask the network-topology-review skill to analyze your module or service dependency graph and identify the highest-risk hubs, cycles, articulation points, and likely blast radius.