The nightly changelog loop

# The nightly changelog loop

## Purpose

A scheduled coding-agent workflow that reviews the previous day's changes and keeps user-facing release history complete and current.

## Prompt

```text
Each night, review changes from the previous day and update the changelog with anything users should know.
```

## When To Use

Use this when a project changes frequently enough that user-facing release notes can drift from merged pull requests, commits, deployments, and product changes.

## Workflow

- 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.

## Verifier

Every user-relevant change from the previous day is accounted for.

The changelog is updated and validated, or the no-change result is recorded.

## Notes

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.

Use the underlying change and product behavior as the source of truth. Commit titles alone can overstate, understate, or misclassify what users experienced.

## Source

- Source: Forward Future Loop Library
- Author: Matthew Berman
- Published: 2026-06-16
- Modified: 2026-06-17
- URL: https://signals.forwardfuture.ai/loop-library/loops/nightly-changelog-sweep/