Loop 008
The nightly changelog loop
A scheduled coding-agent workflow that reviews the previous day's changes and keeps user-facing release history complete and current.
Ready-to-use prompt
Copy the loop
Each night, review changes from the previous day and update the changelog with anything users should know.
Verify / stop
Every user-relevant change from the previous day is accounted for.
The changelog is updated and validated, or the no-change result is recorded.
Context and guidance When to use it, steps, safety notes, and related loops
Use this when
Use this when a project changes frequently enough that user-facing release notes can drift from merged pull requests, commits, deployments, and product changes.
How to run it
- Collect the previous day's merged pull requests, commits, deployments, and other in-scope changes.
- Identify which changes affect users and compare them with the current changelog.
- Add concise dated entries with useful references while preserving existing content and avoiding duplicates.
- Run the relevant checks and record either the validated update or the fact that no user-facing entry was needed.
Why it works
A daily reconciliation makes omissions visible while the context is still fresh. Limiting entries to what users should know keeps the changelog useful instead of turning it into a raw commit feed.
Implementation note
Use the underlying change and product behavior as the source of truth. Commit titles alone can overstate, understate, or misclassify what users experienced.