Create Release Notes

Overview

Generate clear, user-facing release notes from git history and PR descriptions between two versions. Translate technical changes into language that users and stakeholders understand, grouped by impact category with breaking changes prominently highlighted.

Workflow

1. Read project context — Check .chalk/docs/ for:

   • Previous release notes (to match tone, format, and conventions)
   • Product docs (to understand user-facing terminology)
   • Architecture docs (to map technical changes to user-facing features)

2. Determine the version range — From $ARGUMENTS:

   • If two versions are provided (e.g., v1.1.0...v1.2.0), use that range
   • If only a target version is provided, find the previous tag: git tag --sort=-v:refname | head -5
   • If no versions given, use the latest tag to HEAD: git log <latest-tag>..HEAD
   • Run git log --oneline --no-merges <from>..<to> to list all commits