refactor-arch-hotspots

Architectural hotspots are high-churn files, tightly coupled components, and layer violations that slow development. This Skill analyzes your codebase to detect these issues by computing coupling metrics, tracking file churn, identifying import cycles, and prioritizing problems by their impact on feature delivery.

Afferent coupling measures how many components depend on a module; efferent coupling measures how many components it depends on. High efferent coupling creates tight dependencies; high afferent coupling creates broad impact from changes. This Skill computes both to surface instability.

Layer violations occur when components bypass intended architectural layers; dependency cycles create circular imports that block refactoring. This Skill scans your codebase to identify both patterns, flags import cycles, and helps you prioritize fixes based on churn and complexity.

Run hotspot analysis on large, evolving codebases with high churn, complex coupling, or layered architectures where bugs concentrate and refactoring efforts struggle. The Skill surfaces which areas drive the most friction so you can target improvements where they matter most.

Yes. This Skill ranks hotspots by churn, complexity, and impact on feature delivery, so you focus refactoring effort on issues blocking ongoing work rather than scattered low-impact changes.