Skip to content
Computing Life · Share · Yage

A cron job and acceptance criteria can keep a codebase maintained

Boris Cherny's team ran a daily Claude routine that opened 388 PRs over several weeks, with 180 merged into main. The key isn't model smarts—it's the trigger, acceptance criteria, and review funnel working together. Cherny moved the trigger out of chat windows and into a cron job; when output missed the mark, they adjusted the routine definition instead of patching code. The post doesn't disclose whether the 208 unmerged PRs were rejected, duplicated, expired, or queued. A 46.4% merge rate shows candidate submissions naturally outpace actual merges—the review funnel is part of the design.

Why it matters: Boris Cherny's team handed Claude's trigger to scheduled jobs, landing 388 PRs and 180 merges to main in weeks, and when output went wrong they edited the routine definition, not the code.

Read the original ↗Export Markdown