AAWEA.ORG

Manual start

↓

1

Diff since last tag

List commits and user-visible changes since the last release tag or CHANGELOG section.

> git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEAD --oneline
2

Write changelog entry

Add a Keep-a-Changelog entry under [Unreleased]: Added, Changed, Fixed. User-facing language only.
3

Verify format

Confirm CHANGELOG follows project format and links issues/PRs where relevant.

↓

✓

Exit condition: manual

CHANGELOG.md documents all user-visible changes in this ship

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Diff since last tag") S1("Write changelog entry") S0 --> S1 S2("Verify format") S1 --> S2 Exit{"CHANGELOG.md documents all user-visible changes in this ship"} S2 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "Changelog Sync After Ship" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "Changelog Sync After Ship" loop.

Goal: CHANGELOG.md has accurate [Unreleased] entries for this ship
Max iterations: 3
Between iterations run: git log -5 --oneline
Exit when: changelog covers all user-visible changes

Step 1: Review recent commits, write Keep-a-Changelog entries for user-visible changes, and verify completeness.

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.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics