Map source files to layers, components, capabilities, and containers.
npx skills add https://github.com/vishalkhondre/unearth --skill 12-traceability
Please help me install this Agent Skill. Skill: 12-traceability Source: https://github.com/vishalkhondre/unearth/tree/main/skills/12-traceability Command: npx skills add https://github.com/vishalkhondre/unearth --skill 12-traceability
Maps every source file through a traceability chain: file to layer to business component to L1 capability to container. Creates a matrix that answers "which files belong to which capability?" and "if I change this file, what's affected?" Also produces migration guides per component by analyzing extraction difficulty.
Use the traceability pipeline after the Assessment stage to generate the full matrix and per-component views.
High-intent search queries and answers about installing and using this skill.
To map source files to business capabilities for impact analysis, you build a traceability chain linking each file to its layer, business component, L1/L2 capabilities, and container. This exposes how changes propagate across components.
Identifying orphan files before a code migration requires validating completeness across your recon and component mappings. This ensures all production source files are represented in the traceability matrix and highlights unaccounted files for remediation.
Component mapping helps with migration planning by generating per-component traceability views. This shows exactly which files move with a given business component during extraction and analyzes the difficulty of that extraction.
You trace code changes to L1 and L2 capabilities by linking source files through a structured traceability chain. This chain connects individual files to their respective layers, business components, and corresponding capabilities.
You need a trace matrix for architecture discovery when you must understand the structural relationships between files, layers, and containers. It validates that all production source files are accounted for and exposes architectural gaps.
Yes, you can generate migration guides per component using a traceability pipeline. The pipeline analyzes extraction difficulty and produces per-component views showing the specific files that move during extraction.
euCannIdentify and score cybersecurity risks in OSCAL-based systems.
SSiertsemaAnalyze proposed changes across a traceability graph to identify affected artifacts and risks.
janmohammadiGenerate canonical-C4 LikeC4 Context and Container diagrams from ADR-confirmed elements.
Dragoon0xMap JavaScript and TypeScript codebase architecture via import graph regex analysis.
