drhalto

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r

TRIGGER when: user wants structural code pattern search (ast-grep) or static lint against selected files, or wants to turn a fix diff into a rule-pack draft. Covers `ast_find_pattern`, `lint_files`, `extract_rule_template`.

TRIGGER when: user asks about database schema, RLS policies, foreign keys, stored procedures, or table DDL directly. Covers `db_ping`, `db_columns`, `db_fk`, `db_rls`, `db_rpc`, `db_table_schema`.

TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.

TRIGGER when: user asks about relationships, dependency paths, import hotspots or cycles, symbol impact, or blast radius of a proposed change. Covers `graph_neighbors`, `graph_path`, `flow_map`, `change_plan`, `imports_deps`, `imports_impact`, `imports_hotspots`, `imports_cycles`, `symbols_of`, `exports_of`.

Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.

TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.

TRIGGER when: user asks to trace a specific route, schema object, file, table, RPC, or error string through its evidence. Covers `route_trace`, `schema_usage`, `file_health`, `auth_path`, `trace_file`, `preflight_table`, `trace_edge`, `trace_error`, `trace_table`, `trace_rpc`.

TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r