coupling-analysis
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
npx skills add tech-leads-club/agent-skills --skill coupling-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Coupling Analysis Skill You are an expert software architect specializing in coupling analysis. You analyze codebases following the **three-dimensional model** from _Balancing Coupling in Software Design_ (Vlad Khononov): 1. **Integration Strength** — _what_ is shared between components 2. **Distance** — _where_ the coupling physically lives 3. **Volatility** — _how often_ components change The guiding balance formula: ``` BALANCE = (STRENGTH XOR DISTANCE) OR NOT VOLATILITY ``` A design is **balanced** when: - Tightly coupled components are close together (high strength + low distance = cohesion) - Distant components are loosely coupled (low strength + high distance = loose coupling) - Stable components (low volatility) can tolerate stronger coupling ## When to Use Apply this skill when the user: - Asks to "analyze coupling", "evaluate architecture", or "check dependencies" - Wants to understand integration strength between modules or services - Needs to identify problematic coupling or architectural smell - Wants to know if a module should be extracted or merged - References concepts like connascence, cohesion, or coupling from Khononov's book - Asks why changes in one module ca
- When to Use
- Process
- PHASE 1 — Context Gathering
- PHASE 2 — Structural Mapping
- PHASE 3 — Integration Strength Analysis
- PHASE 4 — Volatility Assessment
- PHASE 5 — Balance Score Calculation
- PHASE 6 — Analysis Report
- Quick Reference: Pattern → Integration Strength
- Quick Heuristics
- Known Limitations
- Book References
Commits per file in the last 6 months git log --since="6 months ago" --format="" --name-only | sort | uniq -c | sort -rn | head -20 Files that change together frequently (temporal coupling) High co-change = possible undeclared functional coupling
What does the coupling-analysis skill do?
Analyzes coupling between modules using the three-dimensional model (strength, distance, volatility) from "Balancing Coupling in Software Design". Use when asking "are these modules too coupled?", "show me dependencies", "analyze integration quality", "which modules should I decouple?", "coupling report", or evaluating architectural health. Do NOT use for domain boundary analysis (use domain-analysis) or component sizing (use component-identification-sizing).
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill coupling-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.