Better with Kent · draft

Ship PR

Stop babysitting your agent's pull requests

CI loops
bot triage
Discord handoff

Four words started a war

"I read the code"

Throwaway prototype? Maybe you skip it. Production code you keep? You read it.

Mitchell Hashimoto's post · my reply · ThePrimeagen's take

Meanwhile, your actual afternoon

You are the babysitter

agent opens PR → you refresh CI → you read bots → you push again

The agent implemented the feature. Your attention went to the chores.

Here's the thing

Babysitting isn't reading

Automate the chores

Mark ready, watch CI, triage bots, push again.

Keep the reading

The diff, the risk, the merge call.

Refreshing checks all afternoon isn't reading the code. Automate the loop and spend that attention on the diff.

What I actually want

The handoff should be the output

A summary when CI is clean — root cause, status, links — not another tab to babysit.

If you keep typing the same follow-up on a PR, that follow-up belongs in the loop. Backstory: the loop-engineering episode

While I was at lunch

The Discord ping is the product

  • Production bug: RPC stub used after being disposed
  • Root cause, fix, CI status, preview link — one message
  • CI green — and the agent still said not auto-merged

Example: Cursor Agent + kody#709

Nobody watched this happen

Green checks, live preview

CI passed and a preview URL was posted before I ever opened the PR.

Example: kody#709 checks + preview comment · live preview

Bots pushed back 17 times

Bugbot and CodeRabbit had their say

  • 17 inline bot reviews, 18 commits
  • Address capability alias review findings
  • I never entered the thread

Example: kody#628 — conversation + commit history

It scales

Big diff, still shipped

~8,600 lines across 82 files — reviewed, green, preview deployed.

Example: kody#669 — Files changed + preview comment

Green does not mean merge

The agent judged the risk

Low risk

Squash-merge, watch the deploy, report back.

Everything else

Stop at the Discord ping. I read the diff and decide.

kody#709 changed the sandbox runtime contract — the agent flagged it as worth a human read.

The skill behind the examples

ship-pr

Every PR you just saw ended the same way: "ship this PR."

kcd-skills/ship-pr — one markdown file, installable in any repo

The loop, in plain words

Ready → green → clean → ping

1Mark the PR ready for review.
2Wait for CI — gh pr checks.
3Fix failures in PR scope.
4Triage AI review — fix valid, skip nits.
5Push and repeat until green and clean.
6Ping Discord with the summary.

Inside the skill file

It's just markdown

Invoke with /ship-pr — or end any task with "ship this PR"

## Loop
1. Mark ready — kody:...@kentcdodds/github/pr/set-review-status
2. Wait for CI — gh pr checks
3. Fix failures; address valid AI-reviewer feedback
4. Green and no valid feedback left → break
5. Push → repeat

## Done → Discord
postMessage({ channelId, content })

The value is the stop condition and the handoff — everything else is plumbing.

Not starting from scratch

It composes with skills you have

loop-on-ci + fix-ci + babysit + get-pr-comments

ship-pr orchestrates the smaller skills — each one still works on its own.

Bots are reviewers, not bosses

Triage, don't obey

Fix

Real bugs, CI failures, merge conflicts in your diff.

Skip

Nits, wrong feedback, already-resolved threads.

Blind bot compliance produces churn, not quality.

When failure is an option

Merge mode

squash merge → watch deploy → Discord + links

Say "merge and verify" — genuinely low-risk changes only. Everything else stops at the ping.

Why a skill file

92 times before I named it

92 agent conversations matched this loop before the skill file existed.

I was pasting the same instructions into prompts — a repeated prompt is a skill waiting to be written.

Homework

Ship your next PR with it

  • Copy ship-pr into your agent's skills path.
  • Swap in your own handoff channel — Discord, Slack, whatever pings you.
  • End the next agent task with "ship this PR."

Then spend the time you got back reading the diff.

Better with Kent

This was Better With Kent

Agents make code cheap to write. ship-pr makes it cheap to verify — so you can afford to read it.

Like · comment · subscribe · get better with me