| name | code-explore |
| description | Route code-explore using exact migration registry [{"unit":"code-explore/default","routing":{"negative_boundaries":["Change the request handler to add invoice retries.","Find the commit that introduced this exact regression.","Give a quick answer about where one configuration constant is defined."],"positive_triggers":["Map the architecture and execution flow for the authentication subsystem.","Show how a request travels from the HTTP handler to persistence.","Trace the data flow for invoice creation and identify the key files."]}}]. |
Code-Path Exploration
Build an evidence-backed model of a repository subsystem, execution path, or data flow. Exploration is read-only and emphasizes how pieces connect rather than proposing or applying changes.
Exploration protocol
- Define the entry point, scope, and completion question. Reject absolute paths, traversal, symlink escapes, and ambiguous repositories.
- Start breadth-first: identify top-level modules, public entry points, configuration, tests, and integration seams.
- Follow calls and data transformations in execution order. Record file and symbol evidence at every material hop.
- Inspect alternate paths, errors, asynchronous boundaries, persistence, and external interfaces only where they affect the requested flow.
- Compare implementation with tests and documentation. Label stale documentation, unreachable paths, and inferences explicitly.
- Stop after the requested architecture, execution flow, and data flow can be explained without unresolved high-impact gaps.
A read-only investigator may trace a separate branch of the flow with isolated instructions. Its claims must be checked against repository bytes before inclusion. Do not mutate files, Git state, dependencies, or external systems.
Output
Provide an architecture overview, key files, ordered execution flow, data flow, findings, and residual unknowns. Use a compact diagram only when it makes three or more relationships materially clearer.
Pack handoff
This canonical skill is distributed from the core plugin. Its legacy research-pack payload and pack-ready evidence remain immutable migration provenance and are not a runtime routing surface.
