Bots that read a draft the way an editor would #92

A draft goes out for review, and the only feedback it gets is on the facts, the links, or the code block sitting beside it. Nobody reads it the way a reader will: whether the opening sets up what follows, whether a section wanders, whether the voice contradicts itself halfway through. Nothing fails, so it ships reading exactly as it did on the first pass.

Whether a transition is awkward or a paragraph should be cut is a judgment call, not a rule a gitbot can resolve on its own. What it can do is read the draft the way an editor would and bring the writer every place flow, clarity, or style falls short, with enough of the why that the writer can decide quickly instead of rereading the whole thing cold.

We'd take bots across kinds of draft: a blog post, a release announcement, a conference talk, and a product update each read differently.

New here? gitbot runs Claude Code, Codex or OpenCode as reusable bots on your own machine, with your logins and your files. You define a bot once, a name and a job in plain English, and run it in as many folders as you like.

npm install -g @gitbot-hq/gitbot
gitbot start

Built one for this? Finished bots go into this library, each listed under the GitHub account that built it. In GitBot, the share menu on a bot has a Publish to Marketplace option that opens the pull request to add it. Your instructions go in as written.

These stay open after the first bot lands. And yours doesn't need to be general: people install the bot that's built for the stack they're already on.