Andrew Nesbitt Skewers AI Bot Bait

The piece is parody on the surface, but it lands because it describes the exact signals AI agents reward. If a repository is underspecified, high-friction for humans, and easy to churn, the bots will absolutely show up.

• –The checklist is intentionally perverse: vague issues, generous backlogs, permissive branch rules, and AI-welcoming docs all lower the friction for automated PRs.
• –The `node_modules` and known-vulnerability bits hit closest to reality, because they create endless cleanup work that looks useful to agents even when it is mostly noise.
• –The post's origin matters: Claude helped write it and the author merged it, so the satire doubles as a live demonstration of the workflow it mocks.
• –HN reactions split between spotting the joke and treating it like strategy, which is probably the best evidence that repo metadata is already becoming part of the AI contribution game.