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).

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-tool-design 456,653 ★
  Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and E
• code-review 323,485 ★
  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does th
• codebase-design 323,485 ★
  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interfac
• domain-modeling 323,485 ★
  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLO
• implement 323,485 ★
  Implement a piece of work based on a spec or set of tickets.