I shipped 122 PRs in 24 hours straight out of my software factory, mostly while I was doing something else. Here's the system that lets agents file their own friction, make good PRs, catch their own mistakes, and keep the blast radius small.
Here's what 122 PRs in one day looks like: https://github.com/kentcdodds/kody/releases/tag/v2026.10.11
- (00:00) - 122 PRs in 24 hours
- (00:17) - Agent-filed friction, agent-shipped fix
- (00:51) - Agents work around friction
- (01:41) - The ship PR skill files friction
- (02:43) - Lauren Tan: 2,500 PRs a month
- (03:43) - Three pillars of confidence
- (04:19) - Sponsor: Devin
- (05:35) - Good PRs: decisions directory
- (06:06) - Primitives catalog
- (07:11) - control Kody CLI for self-verification
- (08:24) - System recap on every PR
- (09:24) - Catch mistakes: the ship PR package
- (10:00) - AI reviewers: Bugbot, CodeRabbit, Devin
- (11:07) - Merge, watch deploy, Discord report
- (12:19) - Limit blast radius: feature flags
- (13:46) - Disaster recovery
- (14:33) - Cleanup: agents don't love deleting code
- (15:28) - Dogfooding and product decisions
- (16:31) - Pipe signals in: Sentry, errors, feedback
- (18:00) - Nightly and weekly agents
- (18:35) - Recap
Better with Kent - durable skills for people who ship software.
Thank you to Devin (Cognition) for sponsoring this episode: https://10xn.link/kcd-cognition
Agents don't fix friction. They work around it, and those workarounds compound across every agent touching your codebase. The fix is to turn your agents into complainers: the ship PR skill ends every merge by filing friction, and other agents come through and fix it - sometimes while you sleep.
Kent walks the three pillars that make that safe: (1) good PRs in the first place (a decisions directory, a primitives catalog, the control Kody CLI for self-verification, and a system recap on every PR), (2) catch mistakes before prod (the ship PR package, CI, CodeRabbit, Cursor Bugbot, Devin AI review, preview deploys), and (3) limit the blast radius (feature flags with success metrics, disaster recovery with restore tests). Then cleanup, dogfooding, and signal pipelines from Sentry, runtime errors, user feedback, and nightly/weekly agents.
Agents handle polish, code quality, and implementation. The product vision stays with you.
Links
