coupling-analysis

Quantify module coupling with strength, distance, and volatility metrics.

Updated Jun 18, 2026

Search Tags:#dependencies #coupling #volatility #dependency-graph #architecture-analysis #architecture-health

Ready to run

npx skills add https://github.com/rodrigotoledo/trading-exchange --skill coupling-analysis-rodrigotoledo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coupling-analysis
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28architecture%29/coupling-analysis
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill coupling-analysis-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes software architectures to quantify coupling across modules using a three-dimensional model (strength, distance, volatility), enabling teams to identify high-risk dependencies and guide architectural improvements.

Core Features & Use Cases

Structural mapping of modules and dependencies to visualize the coupling graph.
Distance and strength assessment based on encapsulation levels and architectural boundaries.
Volatility inference leveraging subdomain types and historical signals to prioritize refactors.
Use Case: detect a high-strength, distant, volatile coupling between two services and decide whether to extract a shared contract or duplicate logic.

Quick Start

Run a full coupling health analysis on your codebase to identify critical dependencies and improvement opportunities.

Frequently Asked Questions about coupling-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze architectural coupling and dependency health in my codebase?▼

Architectural coupling analysis identifies high-risk dependencies by quantifying strength, distance, and volatility across module and service boundaries. It constructs a directed dependency graph to produce a balance-score diagnosis and prioritized refactoring recommendations.

What is the best way to measure dependency volatility and strength between services?▼

Measuring dependency volatility and strength involves assessing encapsulation levels, architectural boundaries, and subdomain types. By leveraging historical signals, you can infer volatility to prioritize which service couplings require immediate architectural improvements.

How do I create a directed dependency graph for module-level boundaries?▼

Creating a directed dependency graph for module-level boundaries requires structural mapping of your codebase. This maps inter-module dependencies to visualize the coupling graph, allowing you to assess distance and identify structural issues with severity ratings.

Can I use coupling analysis to decide between extracting a shared contract or duplicating logic?▼

Yes, coupling analysis helps decide between extracting a shared contract or duplicating logic by detecting high-strength, distant, volatile couplings. The resulting executive summary and recommendations guide whether to refactor the boundary or duplicate the code.

What do I need to generate an executive summary of architectural health issues?▼

Generating an executive summary of architectural health issues requires analyzing your codebase's structural dependency map. The analysis identifies coupling issues with assigned severity levels and produces actionable, prioritized recommendations for architectural improvements.