soloopx.by solo lemon.
Back to loops
Docsmanual

Changelog Sync After Ship

After shipping a feature, loop until CHANGELOG.md has a user-facing entry and conventional commits are reflected.

0 views•0 uses•by solo lemon.

// parameters

Triggermanual
Max iterations3
Exit conditionCHANGELOG.md documents all user-visible changes in this ship

// run_this_loop

Copy the kickoff into your agent first. The blueprint below explains how the loop evaluates progress and when it should stop.

Open in CursorOpen in Claude

Use loop copies the kickoff prompt. Share copies the loop link. Open in Cursor / Claude only pre-fill that prompt — they do not install hook files. Download loop saves the loop as changelog-sync-after-ship.md.

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.

// blueprint

The loop contract: target outcome, execution sequence, checks, stopping condition, and safety constraints.

Goal

CHANGELOG.md has accurate [Unreleased] entries for this ship

// loop_sequence

// loop_sequence_diagram.json
closed loop

Trigger

Manual start

Actions block

3 steps
1Diff since last tag
2Write changelog entry
3Verify format

Feedback gate

Evaluate: state progress

Run the check, read the output, then decide whether the loop is complete.

Check failed

Repeat actions with the latest feedback.

Success

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

Safety capMax 3 iterations

// steps

  1. 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. 2
    Write changelog entry

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

  3. 3
    Verify format

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