# Every product update becomes a post worth reading > Every product update becomes a post your buyers can read. Gated before publish. Loop: `changelog-to-content` Category: Product marketing Autonomy: auto+gate License: MIT Source: https://vibemarketers.ai/loops/changelog-to-content Reads the commits or release notes since the last run, discards internal churn, and drafts one post per change a buyer would actually notice. ## What you need - GitHub (read the commit log) ## Goal prompt Give this to your agent. Replace anything in with your own. ``` Read every commit or release note for since . Discard anything with no buyer-visible change: refactors, lint, dependency bumps, internal renames. For each remaining change, draft one post that names what changed, who it is for, and what they can now do that they could not before. Open a PR. Never publish without the gate. ``` ## Verifier prompt Run this as a second, separate agent. It grades the first one's work and must be able to fail. A checker that never fails is not a checker. ``` Read every draft against the commit it came from. FAIL if any post describes a change with no commit behind it, if any post is written for an engineer rather than a buyer, if any number has no source, or if anything published without a PR approval. Otherwise PASS. ``` ## Stopping condition Every buyer-visible change since the last run has exactly one draft naming its commit, one PR is open, and the verifier marks PASS. ## How to run it 1. Save this file into your project, for example `.claude/loops/changelog-to-content.md`. 2. Open your agent in that project (Claude Code, Cursor, or Codex). 3. Paste the goal prompt, with your own values in place of the angle brackets. 4. When it stops, start a fresh session and paste the verifier prompt. 5. Read the verdict before you accept any change. ## What happened when we ran it Last run 2026-09-25 on vibemarketers.ai. - Baseline: 15 commits since 2026-09-17 and no process for turning any of them into something a reader would see. Every shipped change was invisible outside the repo. - Result: 15 commits read, 10 buyer-visible, 5 discarded as internal churn. The 10 include the file downloads, the skills page and the catalog rework. No post was published: this run drafts angles, and the gate is a human. - What this does not prove: A commit subject is a weak signal of buyer impact. A one word subject can hide a large change and a verbose one can hide nothing. This classifies subjects, not diffs. - Cost: 0 human touches, 3 minutes, $0.00 - Raw log: https://github.com/genwfurukawa/vibemarketers-v2/blob/main/lab/runs/2026-09-25-changelog-to-content.json ## Inside a company - Problem it solves: The team ships constantly and nobody outside the team ever hears about it. - Source of truth it reads: The commit log or the release notes, and the Brain for who the buyer is. - What it may do: Read commits, draft posts, open a PR. Never publish, never send. - Who approves: Product marketing approves each draft before publish. - Who owns it: Product marketing lead - How you measure it: Share of buyer-visible releases that got a post, and time from merge to draft. MIT licensed. Copy it, change it, run it. No attribution required.