Developer rejects agent's mixed fix-and-refactor commit, citing Google eng-practices

On November 1, 2026, a post on DEV Community described a situation with an AI coding agent: a bug report said calculateTotal() crashes on an empty order, and the fix was a guard clause at the top of the function. The branch the agent handed back touched seven files. The guard clause was in there, along with amt renamed to amount at every call site, reordered imports, and discount logic extracted into its own piece. The author rejected the branch and asked the agent to split the changes. The post cited Google's publicly available eng-practices code review guidelines, which say a CL should be a single self-contained minimal change, and refactoring should be submitted separately. The surrounding material mentioned a series of Pocket Guides for Developers and an author project called Hermes IDE, but those are personal links, not part of the event. So far this remains a single writer's account plus a guideline reference, with no official response from Google and no follow-up developments.