Analyze codebases for unbalanced coupling across strength, distance, and volatility dimensions.
npx skills add https://github.com/vladikk/modularity --skill review-vladikk
Please help me install this Agent Skill. Skill: review Source: https://github.com/vladikk/modularity/tree/main/skills/review Command: npx skills add https://github.com/vladikk/modularity --skill review-vladikk
This Skill solves the hidden architectural technical debt caused by unbalanced coupling in codebases, which leads to expensive, cascading changes, distributed monoliths, and unpredictable maintenance costs that standard code review tools fail to identify.
Use the review skill to analyze the modularity of the attached project codebase and produce a prioritized list of coupling issues with specific improvement recommendations.
High-intent search queries and answers about installing and using this skill.
You can detect unbalanced coupling by mapping integrations across strength, distance, and volatility dimensions to identify tight dependencies like shared database access that create distributed monolith risks and unpredictable maintenance costs.
Balanced coupling analysis is an architecture review technique that maps integrations across strength, distance, and volatility dimensions to flag unbalanced patterns causing cascading changes and hidden technical debt that standard code review tools miss.
To get actionable recommendations for reducing technical debt, analyze your codebase to produce a prioritized list of coupling issues grounded in the Balanced Coupling model, providing concrete fixes rather than vague architectural feedback.
Yes, you can assess distributed monolith risk by analyzing your codebase to identify modularity imbalances and unbalanced coupling patterns that cause expensive, cascading changes and unpredictable maintenance costs across services.
Standard code review fails to identify architectural technical debt because it does not map integrations across strength, distance, and volatility dimensions to flag the unbalanced coupling patterns that cause hidden, cascading maintenance costs.
The best way to analyze modularity imbalances is to evaluate integrations across strength, distance, and volatility dimensions, producing model-grounded recommendations to improve software modularity and reduce long-term technical debt.
andershi666Clarify repository architecture and code organization for the LobeHub monorepo.
RayzerrekReview Unity gameplay scripts for design quality and maintainability.
rodrigotoledoQuantify module coupling with strength, distance, and volatility metrics.
agnaldo4jDetect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.
