Iflow History Update

issue-flow — history update

Use this skill to decide the changelog bullet as part of /iflow-close. It never runs on its own schedule; it is driven by the "update HISTORY" step, and does not run when the user passed nohistory / skip history. The write happens now, on the issue branch, so the bullet lands in the PR commit.

MODEL & EXECUTION DIRECTIVE

Profile: economy — Prioritize speed and token economy over deep reasoning.

In Cursor: use Auto or a fast model before invoking this step.

Keep scope tight to what this step requires.

Preconditions

1. The changelog file (HISTORY.md) exists at the project root. If it does not, skip this step, print "no HISTORY.md — skipping changelog update" and continue the rest of /iflow-close. Never create the file from this skill.
2. The file is in Keep a Changelog shape: a top-level ## [Unreleased] heading, with released versions below as ## [x.y.z] - YYYY-MM-DD headings. If the shape does not match, stop and report the mismatch instead of guessing — let the user fix the file or pass nohistory.

Inputs from /iflow-close

Operation modes

A. No version bump — append to [Unreleased]

1. Read HISTORY.md. Locate the first ## [Unreleased] heading. The block ends at the next ## [ heading (or EOF).

2. Compose the new bullet:

   - <summary>. (#<N>)

   Summary = log "..." override if provided, else the issue title with sentence case, trailing period trimmed before the . we add.

3. Append the bullet to the end of the Unreleased bullet list. Preserve existing formatting (blank lines, list markers). Do not reorder existing entries.

4. Write the change without a confirm prompt (confirm_changelog_update is false; same as the yolo token's history behaviour). Still report what was written.

B. Version bump happened — promote [Unreleased] to a new release section

Only runs when step 2 of /iflow-close actually changed pyproject.toml to a new version NEW_VERSION.

1. Determine NEW_VERSION (e.g. read from pyproject.toml, or from the uv version command output). Determine TODAY as YYYY-MM-DD in the user's local timezone.

2. Read HISTORY.md. Find ## [Unreleased].

3. Compose the new bullet (same shape as mode A). If [Unreleased] was empty when the bump happened, still create the new release section with this bullet inside it — a version bump implies a release, and the focus issue's bullet is always meaningful.

4. Rename the existing heading from ## [Unreleased] to ## [<NEW_VERSION>] - <TODAY> and add the new bullet at the end of that section's bullet list.

5. Prepend a fresh, empty ## [Unreleased] section above the just-closed release, with one blank line separating them:

   ## [Unreleased]
   
   ## [NEW_VERSION] - TODAY
   
   - …existing bullets from before the promote…
   - <new bullet for this issue> (#N)

6. Write the change without a confirm prompt (confirm_changelog_update is false). Still report what was written.