Vibe Maintainer

A workflow manual written against nearly every instinct OSS culture has drilled into maintainers, by one who cheerfully admits that only agents have ever seen his projects' source code ("no time for field trips"). The transferable part is the vocabulary: named moves like fix-merge, cherry-pick, split-merge, and redesign, each a way to land a flawed contribution the same day with the original author's attribution intact, plus a short list of hygiene rules Steve currently fixes silently and expects to start enforcing with bans. He is honest about the costs. Even with the easy half automated, the whole operation runs 15 to 20 hours a week, and the judgment calls on the last 5–10% of PRs eat hours a day. The case for keeping a human in that loop arrives as a small comedy routine about an agent delivering a glowing, thorough review of a PR that attaches a face-hugging alien to each worker: current models write competent code reviews and still can't be trusted with taste.

The workflow does presume Steve's own tooling — the sheriff runs on Gas Town, and the final third of the essay turns into announcements for its successor, so this is part manual, part roadmap. The stats are self-reported, and the repos in question are five and three months old; whether the method survives contact with a ten-year-old codebase is a question the essay never asks. The stance travels regardless: treat a bad PR as an extraction problem rather than a gatekeeping problem, and bless the forks you can't accommodate — beads_rust got Steve's heartfelt sign-off precisely because it wanted a streamlining the kitchen-sink core would never offer.