My AI Coding Workflow (Revisited) A developer's AI coding workflow now regularly merges 170+ pull requests a day, up from the 100-PR milestone reached after a February 2025 workflow snapshot, with roughly 60% of merged PRs now automerged versus about 25% at the 100-PR mark. The workflow runs around twenty concurrent tasks but caps open PRs to create backpressure, uses a dashboard bot to gather CI/CD status and comments, and has a separate agent rate each PR's risk to decide whether it gets "Merge When Green" or human review. The author reports that zero-touch changes such as typos, help documentation, visual quirks and dependency bumps rose from about a quarter of October merges to closer to 60%. I wrote a snapshot of my AI coding workflow https://jonathannen.com/my-current-ai-workflow/ back in February, as part of the push to 100 PRs a day https://jonathannen.com/building-towards-100-prs-a-day/ . It was explicitly point-in-time, so nine months on, here's the next one. Since then I've hit the hundred https://jonathannen.com/one-hundred-and-fifty/ , and 200 in a day is now a normal day. The core aim hasn't moved: reduce "touches", the number of times I have to pick up a change before it ships. - Zero touches for simple changes: typos, help documentation, visual quirks, dependency bumps. These were about a quarter of what merged in October; they're closer to 60% now. - One touch for a medium feature. I jump in, review, maybe tweak, and away it goes. - More touches for security changes or things the whole team needs to be across. A separate agent rates each PR's risk, from "a robot can approve this" up to "three brains"