component-mapper

What problem does it solve?

Clarifies which parts of a codebase are impacted by a bug or proposed change by identifying affected components, tracing upstream and downstream dependencies, and mapping data flow so engineers can plan safe, focused interventions.

Core Features & Use Cases

• Identify primary and secondary components related to a bug report or improvement request and list file paths and roles.
• Trace dependencies in both directions to reveal callers, callees, external APIs, and data stores that influence or are influenced by the target component.
• Map data flow end-to-end to show where data originates, how it is transformed, where it is validated, and where it is persisted or exposed.
• Use Case: During a bugfix workflow, produce a component map and dependency graph to reduce regression risk and surface documentation gaps before coding.

Quick Start

Use the component-mapper skill to identify affected components, trace upstream and downstream dependencies, and produce a data flow summary for the reported issue.