mako-trace

Mako Trace

Use this skill for focused evidence traces around a known target. The output should help the user understand what implements the target, what depends on it, and what evidence supports the answer.

Targeted Answer Tools

route_trace

Use to find the route handler, nearby files, and evidence for a route/API behavior.

• Best when the user names a route, page, method/path pair, or route-like URL.
• Pair with auth_path for authorization questions.
• Pair with route_context when the user wants a wider route neighborhood.

schema_usage

Use to find where an indexed schema object, table shape, or validation type is defined and referenced.

• Best for schema objects and type-ish entities.
• Use before editing validation contracts or generated schema surfaces.
• Pair with trace_table or table_neighborhood for database-backed entities.

file_health

Use to understand a file's role, dependents, risks, and likely blast radius.

• Best before editing a central or unfamiliar file.
• Pair with imports_impact for a deeper dependency view.
• Do not use it for repo-wide orientation; use repo_map.

auth_path

Use to inspect likely authentication or authorization boundaries for a route, file, feature, or flow.

• Best when the user asks what protects something or whether auth is enforced.
• Pair with route_trace, route_context, and tenant_leak_audit when the risk is tenant or data-boundary related.
• If no exact route, file, or feature matches, auth_path returns matched: false, reason, and a suggested cross_search fallback instead of throwing a batch-breaking error.
• Do not overclaim; report evidence and uncertainty.

Composer Trace Tools

trace_file

Use for a compact file trace: symbols, imports, routes, schema touches, and notable relationships before editing.

preflight_table

Use before changing database-backed behavior to inspect table usage, RLS, relations, and common query paths.

trace_edge