review

Analyze codebases for modularity imbalances using the Balanced Coupling model.

1|1|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/rodolfodpk/spring-crablet --skill review-rodolfodpk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rodolfodpk/spring-crablet/tree/main/.claude/skills/review
Command: npx skills add https://github.com/rodolfodpk/spring-crablet --skill review-rodolfodpk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes codebases for modularity imbalances and produces a review of design issues, helping identify coupling problems and architecture quality.

Core Features & Use Cases

  • Balanced Coupling Analysis: Uses the Balanced Coupling model to assess modularity.
  • Design Issue Identification: Identifies concrete design issues and explains them.
  • Use Case: When reviewing existing code for coupling problems or assessing architecture quality.

Quick Start

Use the review skill to analyze the modularity of the 'source-code' directory.

Frequently Asked Questions about review

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

FAQPage Schema
How do I identify modularity imbalances and coupling problems in my codebase?

To identify modularity imbalances, you can analyze your codebase using the Balanced Coupling model to detect design issues related to knowledge encapsulation, complexity, and cascading changes. This process assesses architecture quality and highlights distributed monolith risks.

What is the Balanced Coupling model for code architecture assessment?

The Balanced Coupling model is an architecture assessment method used to evaluate modularity in a codebase. It identifies design issues by analyzing knowledge encapsulation, complexity, and cascading changes to reveal coupling problems and distributed monolith risks.

How do I perform a code review focused on architecture and design analysis?

Perform an architecture-focused code review by analyzing the modularity of your source code directory to identify design issues. This approach detects coupling problems, evaluates knowledge encapsulation, and highlights potential distributed monolith risks.

Can I use this approach to detect distributed monolith risks in my source code?

Yes, you can detect distributed monolith risks by analyzing your source code for modularity imbalances. The Balanced Coupling model specifically addresses these design issues by identifying cascading changes and poor knowledge encapsulation in the codebase.

When do I need to analyze codebase modularity for design issues?

You need to analyze codebase modularity when reviewing existing code for coupling problems or assessing overall architecture quality. It is essential when you want to prevent cascading changes, improve knowledge encapsulation, and mitigate distributed monolith risks.