Your agent opened the PR. Now you're refreshing CI and arguing with bots. Kent shows the ship-pr skill that closes that loop - mark ready, fix CI, triage review, Discord handoff - so you spend attention on risk, not chores.

• (00:00) - Still reading the code?
• (01:18) - "I read the code" kicked off a war
• (01:51) - I do read the code sometimes
• (02:31) - You're the PR babysitter
• (03:33) - I turned the loop into a skill
• (04:14) - Discord handoff is the product
• (04:33) - When it won't auto-merge
• (05:25) - Inside the ship-pr skill
• (06:16) - The ship-pr loop
• (06:28) - Merge mode (low risk only)
• (07:09) - How far this scales
• (07:49) - The factory spectrum
• (08:58) - Don't ship blind
• (09:43) - 92 times before it was a skill
• (10:20) - Homework: ship a PR
• (11:03) - Sign-off

Better with Kent - durable skills for people who ship software.

"I read the code" kicked off a war. Kent's take: it's a spectrum based on risk. The afternoon killer is not reading - it's babysitting CI, Bugbot, and "please fix that" loops after the agent already implemented the feature.

This episode is the concrete payoff after loop-engineering: real Discord handoffs from Kody (including a medium-risk PR that stayed unmerged on purpose), the ship-pr skill file, merge mode for genuinely low-risk changes, and the 92-times lesson before formalizing a skill.

Homework: tighten your ship loop. On a simple change, let the agent merge and verify - if your team is good with that.

Links

• Watch on YouTube
• kcd-skills / ship-pr
• kody#709 - medium-risk handoff (no auto-merge)
• kody#628 - bots + merge by kody-bot
• Mitchell Hashimoto - "I read the code"
• Kent's reply on the spectrum
• I Was Doing Loop Engineering Before It Had a Name
• Better with Kent