geo-first

Trace from a reproduced symptom to the source code that causes it. Identify the specific file and approximate line, then rate confidence honestly.

Write the fix when verify says bug and diagnose says high confidence. Follow EmDash conventions, confirm the reproduce test now passes, run lint and typecheck, stage but do not commit.

Decide whether the diagnosed behaviour is actually a bug or whether the code is doing what it was designed to do. Gate the fix stage.

Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.

Use when the user asks to inspect files, modify code, create files, or install dependencies/packages directly as part of implementation work. Prefer acting end-to-end instead of stopping at analysis.