14 releases in 12 weeks, 15 agents, every draft gated by a human in Git.

Every DevTools audit I ran in spring 2026 hit the same wall: marketing content lagged what engineering had already shipped. Release notes came a week late, the blog described last quarter's API, and the "AI search visibility" fixes I recommended kept pointing at the same root cause, which was that nobody owned the moment of release. I wanted the release itself to be the trigger, the pull request to be the unit of marketing work, and a human review in GitHub to be the only way anything goes out.

A Python CLI, pipx install devrel-origin, MIT-licensed, bring your own Anthropic or OpenRouter key. It scaffolds a .devrel/ directory in the repo, reads the diff, the AST, the docs and the last six release notes, and on a new tag drafts the release note, changelog entry, blog post, social thread and email digest as files in a marketing PR. Fifteen named agents split the work (health, DevRel, sales), an eight-stage editorial pipeline runs voice, style and a slop blocklist over every draft, and the grounding stage added in v0.3.0 makes every factual claim resolve to a repository fact or a knowledge-base source, with --cut-unsourced removing the ones that cannot. The draft and its trace record are committed together, so a reviewer can see which source backs which sentence. Nothing autopublishes; the merge is the moment marketing happens. I dogfooded it on its own repo from the first release: the first days of production runs surfaced silent failures, a five-minute wall-clock timeout and a test suite that had been passing against its own mocks, and each fix shipped as a release with its own hand-written, reviewed changelog entry. Four public example deliverables, generated against the PostHog repository and stored with their trace files, are the proof room on the site.