architectural-hotspotslisted

Surfaces architectural hotspots in a codebase — high-coupling hub files, tangled high-fan-out modules, oversized god modules, and dependency cycles. Use this skill when the user asks where to refactor, which files are architecturally problematic, which modules are most tightly coupled, where the tech debt is concentrated, what should be split up, or how the dependency structure of a project looks. Also trigger on phrases like "find hotspots in this repo", "coupling problems", "god classes", "circular dependencies", "refactor candidates", or "which files do too much" — even if the user does not say the word "architecture". Do NOT trigger for runtime *performance* hotspots — "why is my app slow", "profile this", CPU/memory bottlenecks — this skill sees structure, not execution; for static perf findings use `code-audit-deep`, for real measurements suggest a profiler. This skill is **scope: whole repository**. If the user is pointing at a specific file or asking what is wrong *inside* a file ("hotspots in commit.
Stoica-Mihai/claude-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill Stoica-Mihai/claude-skills

# Architectural Hotspots Static dependency-graph analyzer that ranks files along five orthogonal dimensions instead of inventing a single composite score: - **Hubs** — many other files depend on them (high fan-in). - **Tangles** — they depend on many other files (high fan-out). - **God modules** — large files concentrating too much responsibility. - **Churn** — files most frequently touched by commits (git repos only). - **Cycles** — strongly-connected components of size > 1 in the import graph. Each dimension answers a different question; the human reader combines them. A file showing up in **two** sections is more interesting than one with a high score in any single dimension. ## When to run this Run it when the user is asking a *strategic* question about the codebase — "where should I start refactoring", "what's tightly coupled", "is this app architecturally sound", "which files keep biting us". Do not run it for narrow questions about a specific file or function. Skip it on: - Single-file edits or bugfix tasks. - Codebases with fewer than ~30 source files — the analyzer needs scale to be useful, and on small repos the user can read the structure directly. - Repos that are mostly generated code or templates. ## How to run The analyzer is a single Python 3 script with no third-party dependencies. ```bash python plugins/architectural-analysis/skills/architectural-hotspots/scripts/find_hotspots.py <repo_path> ``` Useful flags: - `--top N` — rows per section (defa