# AI wrote most of my merged PRs. Last night I typed four lines myself.

> Source: <https://dev.to/connabyss/ai-wrote-most-of-my-merged-prs-last-night-i-typed-four-lines-myself-5of>
> Published: 2026-11-20 19:34:12+00:00

**Recommendation:** After an AI agent claims a bug is fixed, revert that commit and rerun your tests; if they still pass, no test guards the fix and you need one.
More in the playbook "Working with AI coding agents": <https://wpnews.pro/playbooks/coding-agents>

This week, maintainers merged three of my pull requests into projects I don't own. Then, a little before midnight, I typed my first fix by hand.

It was four lines. I was nervous anyway.

I'm new. Not "new to Rust" new. New new. Most of the code under my name was typed by Claude Code. My job so far has been the part after the AI says "fixed": running it, checking it, and asking whether anything would notice if it was wrong.

That habit turned into a tool, [Bite](https://github.com/connabyss/bite). It takes a "fixed" commit back out of your code and reruns your tests. If they still pass, no test guards that fix.

This week I decided "checking the AI" isn't the same as knowing how to code. So I started learning.

My language project, [Past Forever](https://github.com/connabyss/past-forever), has a command-line runner. When a program crashed, the runner printed the error and then told the computer everything went fine. Exit code 0. Any script or CI job running it would shrug and carry on.

Here's the whole fix ([PR #27](https://github.com/connabyss/past-forever/pull/27)):

``` js
-  console.log(F.text(src, { why }));
+  const result = F.text(src, { why });
+  console.log(result);
+  if (result.includes('stopped: ')) process.exitCode = 1;
```

Claude walked me through it step by step. I typed every character in the GitHub web editor, ran the tests, and then had to explain it back in my own words before merging. My explanation was one sentence. It counted.

What I learned: a program has two ways of answering. What it prints is for people. The exit code is for other programs. Mine was lying to the programs.

**[docling-pipelines #686](https://github.com/docling-project/docling-pipelines/pull/686)** (merged). The reviewer asked for five changes. One was that when you escape text, "the backslash must be escaped first." I pushed one commit that covered every point, and it was approved the same day.

**[django-modeltranslation #831](https://github.com/deschler/django-modeltranslation/pull/831)** (merged). Bite found this one: two settings helpers reset a value to nothing when they finished, instead of putting back what was there before. I opened it on October 27. It sat for three weeks. I sent one polite nudge. It got merged this week.

**[django-modeltranslation #832](https://github.com/deschler/django-modeltranslation/pull/832)** (merged). The maintainer requested a change: don't patch Django when the file loads, do it in the app's `ready()` step, with a guard so it only happens once. I made the change, added a test, and it was merged the same day. My PR description said up front that I wrote it with help from Claude Code.

[wardenIQ](https://github.com/adlerqa/wardeniq) is a test-case generator that can run on a local AI model. I test it on a CPU-only setup, which turns out to be useful: I'm the slow machine.

Outside contributors have been helping on my repos for weeks. This week two more showed up.

[imshah-id](https://github.com/imshah-id) opened [Trawl PR #28](https://github.com/connabyss/trawl/pull/28). I reviewed it and asked for changes. The day before, I was the one getting change requests.

[jeelthacker1](https://github.com/jeelthacker1) asked to take [Bite #251](https://github.com/connabyss/bite/issues/251). I said it's theirs.

AI did most of the typing in everything above, and helped draft this post. Every link and number in it was checked against the source. The week's real change is that I'm starting to read what it writes, and sometimes write it myself.

If you're also learning with an AI next to you: make it explain, then explain it back. And check its "fixed" claims. Some of them don't hold.

I credit everyone who breaks something. There's a [Hall of Fame](https://github.com/connabyss/past-forever/blob/main/HALL_OF_FAME.md) with a Breakers list.

`pipx install bite-check`, then `bite --free`.
Small issues, each written to be a good first one:

I'm [connabyss on GitHub](https://github.com/connabyss). I post here when something breaks or ships, which this week was both.
