component-identification-sizing

Identify architectural components and calculate size metrics from directory and namespace structures.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Matheusrlr/payment-orchestrator --skill component-identification-sizing-matheusrlr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-identification-sizing
Source: https://github.com/Matheusrlr/payment-orchestrator/tree/main/skills-catalog/skills/%28architecture%29/component-identification-sizing
Command: npx skills add https://github.com/Matheusrlr/payment-orchestrator --skill component-identification-sizing-matheusrlr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers and architects understand the size and structure of their codebase, identifying components that are too large or too small, which is crucial for planning refactoring and decomposition efforts.

Core Features & Use Cases

  • Component Identification: Automatically detects architectural components based on directory and namespace structures.
  • Size Metrics: Calculates accurate size metrics using executable statements, not just lines of code.
  • Oversized/Undersized Detection: Flags components that deviate significantly from the average size, suggesting areas for splitting or consolidation.
  • Use Case: When planning to break down a monolith, use this Skill to get an inventory of all components, their sizes, and recommendations on which ones are candidates for extraction into microservices.

Quick Start

Use the component identification and sizing skill to analyze all components in the current codebase.

Frequently Asked Questions about component-identification-sizing

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

FAQPage Schema
How do I identify oversized components in a codebase for refactoring?

Component identification analyzes directory and namespace structures to detect architectural components, then calculates size metrics using executable statements to flag oversized or undersized areas for refactoring.

What is the best way to measure codebase structure and size for monolithic decomposition?

Measuring codebase structure for monolithic decomposition involves analyzing directory structures and calculating executable statement counts to produce an inventory of components and their complexity.

How do I know which components to extract into microservices when breaking down a monolith?

To identify microservice extraction candidates, analyze component size metrics to flag components that deviate significantly from the average size, indicating they should be split or consolidated.

How are component size metrics calculated during codebase analysis?

Size metrics are calculated using executable statements rather than raw lines of code, providing a more accurate representation of component complexity and granularity for architectural assessment.

Can I detect undersized components in my codebase for consolidation?

Yes, codebase analysis detects undersized components by calculating size metrics and flagging those that fall significantly below the average component size, suggesting them for consolidation.