afc:release-notes

/afc:release-notes — Generate Release Notes

Rewrites commit/PR history into user-facing release notes and optionally publishes to GitHub Releases. This is a standalone utility — not part of the auto pipeline. Does NOT modify local files (CHANGELOG updates are handled by /afc:launch).

Arguments

• $ARGUMENTS — (optional) Version range and flags
  • v2.3.0..v2.4.0 — specific tag range
  • v2.4.0 — from that tag to HEAD
  • Not specified — auto-detect last tag to HEAD
  • --post — publish to GitHub Releases after preview (can combine with any range)

Parse the arguments:

1. Extract --post flag if present
2. Parse remaining as version range:
   • If contains ..: split into {from_tag}..{to_tag}
   • If single version: use {version}..HEAD
   • If empty: auto-detect with git describe --tags --abbrev=0

Git Context (auto-loaded)

!git describe --tags --abbrev=0 2>/dev/null || echo "[NO_TAGS]" !git log $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD --pretty=format:"%H %s" --no-merges 2>/dev/null || git log --pretty=format:"%H %s" --no-merges

Execution Steps

1. Determine Range

• If a tag is found, set from_tag to that tag, to_tag to HEAD
• If no tags exist, inform the user: "No tags found. Include all commits? (y/n)"
• If a to_tag is specified (not HEAD), verify it exists: git rev-parse --verify {to_tag} 2>/dev/null
• Determine the version label for the notes header:
  • If to_tag is a version tag: use it (e.g., v2.4.0)
  • If to_tag is HEAD: use "Unreleased" or the from_tag bumped (ask user)

2. Collect Raw Data

Run these commands to gather change context:

# Commit history (no merges)
git log {from_tag}..{to_tag} --pretty=format:"%H %s" --no-merges

# Merged PRs since the from_tag date
from_date=$(git log -1 --format=%aI {from_tag})
gh pr list --state merged --search "merged:>$from_date" --json number,title,author,labels,body --limit 100

If gh is not available or the repo has no remote, skip PR collection — proceed with git-only data.