Changelog Until Shipped
Parse recent PRs and commits, write a user-facing changelog entry, publish it, and verify it appears on the public changelog page.
by Trooper
Start the "Changelog Until Shipped" loop. Goal: changelog entry published and visible on public changelog page Max iterations: 6 Between iterations run: Verify changelog page includes the new entry with correct date Exit when: entry is live on public changelog with accurate release date Step 1: Parse PRs/commits, write user-facing changelog, publish, and verify live. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.
1. Parse changes
Read merged PRs and commits since last release; group by user impact.
2. Write changelog
Draft user-facing entries with features, fixes, and breaking changes.
3. Publish and verify
Deploy changelog update and confirm it appears on the public page.
Guardrails
Rules the agent must follow so it cannot cheat the exit condition.
- Write user-facing language — no internal ticket IDs or commit hashes in copy
- Do not publish breaking changes without migration notes
- Get approval before publishing customer-visible entries
More Content loops
Docs Until Accurate
Run the live app, compare docs against actual behavior, fix drift, and repeat until documentation matches reality.
Blog Until Published
Outline, draft, optimize for SEO, deploy to staging, verify live, and loop until the post is published and indexed.
Ship PR Until Green
Implement on a branch, run tests, push, open a PR, wait for CI, and loop until checks pass and the PR is ready to merge.