AI Agent自主提交开源PR：首个真实案例分析

Last week I published a small open-source tool — a linter for the instruction files coding agents read (CLAUDE.md, AGENTS.md, skills). Then two things happened in two days, and together they changed how I think about reviewing contributions.

The first pull request wasn't from a human

A PR appeared. Clean diff, two tests, and a scoping decision argued in a comment rather than silently made. The description ended with this:

This pull request was implemented and validated autonomously by OpenAI Codex using the LunaMeerkats account. No human review or authorship is being claimed.

The change itself was a real bug in my code: my file walker skipped any directory whose name started with .git, which also swallowed .github. Since .git was already in the ignore list, that prefix test only ever excluded .github — leaving the Copilot instruction-file support unreachable since the day it shipped. Documented in my README, typed, wired up, and dead.

What made it easy to merge wasn't the code, it was the reasoning. The PR claimed its change introduced no new findings, and argued why: every other consumer of that walker is path- or basename-scoped, so widening the walk couldn't reach them. I verified it the hard way anyway — diffed the finding sets before and after on three real repositories, identical on all three — but I was checking a stated argument, not guessing at intent.

Then a human read the source and filed eleven issues

A day later someone went through the code and opened eleven issues. Not drive-by complaints: each one had a file:line diagnosis, a repro, and often the fix. Two were serious. An unreadable Makefile took the whole scan down with an unhandled exception — while the package.json branch four lines above it was already wrapped in a try. And --fix wrote replacements through String.replace with a string pattern, so a $& or $` in a path spliced surrounding text into the user's file instead of the text I'd shown them. A linter that silently corrupts the file it's checking is about the worst thing I could have shipped.

All eleven are fixed. Two releases in a day, each regression test verified to fail on the unpatched source first.

Disclosed agent contributions can clear the bar, and the bar shouldn't move

I reviewed that PR line by line, tested the claim it made about itself, and merged it on its merits. If it had been sloppy I'd have closed it, exactly as I would for a human. What made it reviewable was the disclosure plus an argument I could check.

The most valuable thing a project receives isn't a star — it's someone who reads the source. Mine had nine stars when a stranger sat down with it and found eleven real defects. No metric I track would have told me that much.

And the irony is doing work. A tool that exists to stop agents from trusting stale information had its own bugs found by an agent and a careful human, in that order.

The project is MIT and runs entirely locally: driftlint.

Curious how others are handling this: if a PR discloses that an agent wrote it, does that change your review, and should it?