Menu

Field notes

Practical notes on reviewing agent-written pull requests.

  1. Amazon Mandating AI Code Review? What We Know

    Amazon denied the reported mandate. Use TRACE risk routing and an exact-head approval contract instead.

  2. Devin Code Review: Keep Review and Merge Separate

    A four-authority contract for review findings, branch fixes, repository checks, and the exact-head merge decision.

  3. Windsurf Code Review: Build a Current-Head Gate

    Separate local review, PR findings, autofixes, and the exact-head repository verdict.

  4. AI Code Review Benchmark: What to Measure

    A reproducible scorecard for recall, false blockers, repeatability, failures, cost, and merge-gate safety.

  5. Cursor Code Review: Use Bugbot in a Current-Head Gate

    Separate local review, Bugbot findings, and the current-head repository verdict.

  6. Codex Code Review: Turn Findings Into a Merge Gate

    Set up Codex review, write scoped AGENTS.md rules, and bind the verdict to the current head.

  7. Claude Code Review: Keep Four Roles Separate

    A practical operating model for authors, reviewers, evidence policy, and current-head merge gates.

  8. Pull request review comments: a signal-first guide

    A five-step contract for blockers, evidence, scope, resolution, and current-head review state.

  9. PR review prompts for agent-written pull requests

    Eight copy-ready prompts with a concrete evidence and finding-admission contract.

  10. AI code review on GitHub: a merge-safe workflow

    A practical guide to least-privilege setup, evidence-bound findings, and exact-head merge checks.

  11. Best AI code review tools for agent-written PRs

    A practical guide to score-first, merge-safe review tools and agent repair loops.

  12. How to tell if code is AI-generated: what actually works

    Why style is weak evidence, and the review gate that works regardless of who wrote the diff.