Tools · Reef Engine

Reef Engine tools

Reef is the durable fact and finding layer. These tools query and update what Mako already knows about a project — across sessions. Read first, ack last.

project_findings read

Active durable findings for the project. "What's on fire?" view across all files.

file_findings read

Findings attached to one file. Read this before editing a sensitive file — someone may have already analyzed it.

Input

{ "filePath": "lib/auth/dal.ts", "limit": 50 }

project_facts read

Lower-level facts behind project findings. Useful when a finding cites a fact you want to inspect.

file_facts read

Indexed facts for one file (symbols, exports, imports, route mappings).

project_open_loops read

Unresolved findings, stale facts, and failed diagnostic runs in one view.

verification_state read

Whether cached diagnostics still cover current working-tree facts. Tells you if "everything's fine" is current or stale.

project_conventions read

Discovered auth guards, runtime boundaries, generated paths, route patterns, and schema usage conventions.

When to use it

Onboarding the agent to project rules without re-reading the codebase.

rule_memory read

Rule descriptors plus finding history. Useful when investigating recurring lint patterns.

reef_instructions read

Scoped .mako/instructions.md and AGENTS.md instructions for requested files.

project_index_refresh write

Run the project indexer and report freshness changes.

Input

{ "mode": "if_stale", "reason": "after batch of edits" }

Use mode: "if_stale" for the cheap path. mode: "force" only when indexed answers look wrong.

working_tree_overlay write

Snapshot working-tree file facts (existence, hash, size) without reparsing AST/imports/routes/schema.

finding_ack write

Mark a finding as reviewed-safe in the local ledger. Don't ack noise — acks are a real review action.

Input (from lint_files)

{
  "category":     "<finding.code>",
  "subjectKind":  "diagnostic_issue",
  "filePath":     "<finding.path>",
  "fingerprint":  "<finding.identity.matchBasedId>",
  "reason":       "Reviewed false positive because ...",
  "sourceToolName": "lint_files",
  "sourceRuleId": "<finding.code>"
}

finding_ack_batch write

Same payload shape as finding_ack, applied across many findings in one call. For sweeping reviews.

finding_acks_report read

Report on what's been acked. Run this before assuming a clean diagnostic result means no one suppressed anything.