gen-release-notes

# Release Notes Generator Generate professional release notes following the Keep a Changelog standard. **Input**: Previous tag (e.g., `v0.0.1`) ``` $ARGUMENTS ``` --- Use extended thinking to analyze the changes thoroughly before generating release notes. ## Gates Do not invent tags, PR numbers, or links. Each row must pass before the work that depends on it. | When | Pass condition (evidence) | On fail | |------|---------------------------|---------| | Before `git log` / `git diff` | `git tag -l "$PREV_TAG"` prints exactly one line matching `PREV_TAG` | Stop; report that the tag is missing—do not write changelog entries | | Before categorizing | `git rev-parse "$PREV_TAG^{commit}"` exits 0 | Stop; fix `PREV_TAG` or repo checkout | | If using `gh pr list` | Command exits 0 and JSON is valid | Fall back to commit subjects + merge-commit URLs only; do not fabricate PR numbers | | After Step 5 footer edits | Step 6 footer-gate exits 0 (both `grep -q` checks pass against the staged `CHANGELOG.md`) | Re-run footer edits from Step 5, then re-run Step 6 until it exits 0 | ## Step 1: Gather Changes Run these commands to collect information about changes since the provided tag: ```bash # Store the previous tag PREV_TAG="$ARGUMENTS" # Gate: tag must exist (output must be non-empty and match PREV_TAG) git tag -l "$PREV_TAG" # If the line above prints nothing, STOP — do not continue below. # Get the repo URL for PR links git remote get-url origin # List commits since last t...