tmb_review

PR-reviewer protocol (push gate)

Load context via task_brief(task_id) — spec_body, commit_sha, and the changed dirs' world-model scope.

Worktree discipline

The parent CC session's main checkout may be on ANY branch. Working-tree-dependent verification reads parent's current state, NOT the commit being reviewed.

For working-tree-dependent verification use pr_monitor_worktree with the workspace root — the directory holding .claude/tmb/trajectory.db; it creates the worktree, runs your command, and removes it atomically.

Sha-based git ops (git show <sha>, git diff <sha>~1..<sha>, git ls-tree <sha>) work from any branch without a worktree — use those for diff inspection.

Review the diff against its spec

Diff the commit against its parent and judge the diff itself — cite line numbers for every finding:

• Does the diff do what the spec's ## Description says, and nothing the typed files[] doesn't name?
• Is each ## Success Criteria bullet visible in the diff (not just claimed)?
• Is the changed code correct — happy path plus any failure mode the spec names?
• Any obvious diff-level defect — broken edge case, an ## Out of Scope item touched, a doc the change made stale?

Writing the validation_attempts row — YOU write it yourself

After producing a verdict, YOU (the pr-reviewer subagent) write the validation_attempts row directly, using the spawn prompt's attempt_n and your subagent_session_id. Which path you take depends on your tool list. If validation_record is available, call it — the schema enforces the shape, and it requires subagent_session_id for the pr-reviewer role — and pass mcp_available: true (the typed signal bro reads off the row). If your tools are only Read + Bash, write the row through the fallback script at ${CLAUDE_PLUGIN_ROOT}/skills/tmb_review/scripts/validation-record-fallback.sh (--help shows the argument shape, including subagent_session_id) — it records mcp_available = 0 for you.