Mako Discovery

To locate a feature in an unfamiliar codebase, use repository orientation to map symbols, routes, and schema before editing. This approach identifies the correct discovery path and specialist search tools to pinpoint implementation targets across multiple file types.

Choosing a code search tool for cross-file impact questions requires evaluating whether you need broad repository orientation or targeted tracing. Select a discovery tool when the entity type is unclear, switching to specialist search tools once the implementation target is identified.

Orienting in a new repository involves scanning across code, routes, schema, diagnostics, and findings to locate specific tables or files. This discovery process establishes a repeatable workflow path before you apply targeted tracing to the codebase.

Repository orientation is needed when you are working in an unfamiliar codebase and do not yet know where a symbol or feature lives. It provides the necessary discovery path across code and schema before a direct code search can be effectively executed.

Yes, you can use discovery tools to plan a repeatable workflow for codebase diagnostics and findings. They help identify whether to start with broad repository orientation or a specialist search tool to safely review context before making edits.