Map internal container components, layers, and dependency relationships.
npx skills add https://github.com/vishalkhondre/unearth --skill 05-components
Please help me install this Agent Skill. Skill: 05-components Source: https://github.com/vishalkhondre/unearth/tree/main/skills/05-components Command: npx skills add https://github.com/vishalkhondre/unearth --skill 05-components
Provides a structured deep-dive into a single container, revealing its internal structure at the C4 component level. It identifies business components (domain logic units), technical components (cross-cutting infrastructure), internal layers, god classes, test coverage gaps, and business rules. It maps intra-container dependencies and component-to-external-system connections. This skill is repeatable -- run it once per container selected for analysis. Use after 04-containers when you need to understand what's inside a specific deployable unit before extracting capabilities.
Run a focused, container-level analysis to reveal internal structure and dependencies for downstream capability extraction.
High-intent search queries and answers about installing and using this skill.
Analyze container internal structure by identifying business and technical components across presentation, application, and data access layers. This exposes dependencies, architectural boundaries, and hotspots at the C4 component level.
Container traceability is the structured mapping of internal business rules and technical components within a deployable unit. It produces an artifact detailing boundaries and dependencies to assess readiness for capability extraction.
Identify god classes and test coverage gaps by analyzing the container's internal layers and dependency relationships. This assessment reveals cross-cutting infrastructure components and governance hotspots requiring modernization.
You need container analysis when assessing coupling, test coverage, and governance before extracting business capabilities. It exposes dependency hotspots and component boundaries to inform architecture decisions and modernization plans.
Yes, component mapping is repeatable and designed to run once per container selected for analysis. This per-container repeatability supports governance traceability and structured modernization across your deployable units.
lagz0neMap Context-defined interfaces to container components and produce architecture artifacts.
leaderiopEnforce clean-architecture boundaries between React UI and domain logic.
FlyFireFGenerate dark-themed architecture diagrams as HTML with embedded SVG graphics.
brand6Audit test evidence and QA documents for coverage, readiness, and traceability.
