skills.rest
alexjcm
alexjcmCOMMUNITY
Explore all skills by this author →
Website𝕏@alexjhcmGitHub

component-identification-sizing

Identify architectural components and compute size metrics for decomposition planning.

Updated Mar 12, 2026
Search Tags:#refactoring#standard-deviation#architecture-decomposition#component-identification#codebase-sizing#component-inventory#statements-metrics
One-click install
npx skills add https://github.com/alexjcm/agent-skillset --skill component-identification-sizing-alexjcm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: component-identification-sizing
Source: https://github.com/alexjcm/agent-skillset/tree/main/skills/arquitecture/component-identification-sizing
Command: npx skills add https://github.com/alexjcm/agent-skillset --skill component-identification-sizing-alexjcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies architectural components in a codebase and calculates size metrics to assess decomposition feasibility and identify oversized components.

Core Features & Use Cases

  • Leaf components discovery by traversing directory/namespace structures and ensuring only leaf nodes are treated as components.
  • Size metrics calculation: statements, files, and percentage of codebase; computes mean and standard deviation for outlier detection.
  • Oversized/undersized component detection with actionable split or consolidation recommendations.
  • Automated component inventory generation including component paths and sizes.
  • Guidance for applying decomposition patterns and governance during refactoring.

Quick Start

Identify leaf components and generate a size-based inventory to begin decomposition planning.

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 architectural components in a codebase for decomposition planning?▼

Component identification for decomposition involves traversing directory structures to discover leaf nodes, counting executable statements, and calculating percentage shares to generate a component inventory.

What is the best way to detect oversized components in a monolithic codebase?▼

Detect oversized components by calculating size metrics such as executable statement counts, then computing mean and standard deviation to identify statistical outliers requiring splits.

Can I use component sizing metrics on a codebase written in any programming language?▼

Yes, component sizing is applicable to codebases of any programming language because it maps directory structures and counts executable statements regardless of the underlying tech stack.

How do I generate a component inventory with size metrics for refactoring?▼

Generate a component inventory by mapping leaf components, counting files and executable statements, computing standard deviation, and producing split or consolidation recommendations for refactoring.

When do I need standard deviation metrics for component identification?▼

Standard deviation metrics are needed during component identification to detect outliers, highlighting oversized components requiring splits or undersized components suitable for consolidation.

Related Skills

Explore More Software Engineering Skills→
P4rziP4rzi

component-identification-sizing

Identifies and measures codebase components by namespace and file counts.

Community
Intermediate
rodrigotoledorodrigotoledo

component-identification-sizing

Identify architectural components and quantify their size using statement counts.

Community
Intermediate
ddsyasasddsyasas

components

Identify and enforce cohesive, decoupled component boundaries in software systems.

Community
Advanced
wesleyegbertowesleyegberto
3

microservices-architect

Define service boundaries for distributed systems using domain-driven design.

Community
Advanced