Release Note Writer

Core Rule

Write release notes in English only. Convert technical history into reader-facing changes grouped by audience and outcome. Do not mirror commit scopes directly.

Required Discovery

Before drafting, gather the release context:

1. Check the current repo version and tags.
   • Inspect package/version files that already exist in the repo.
   • Inspect recent git tags with git tag --sort=-v:refname.
   • Identify the previous release tag.
2. Run changelogithub dry output:
   • pnpm dlx changelogithub --dry --from <previous-version>
   • If the command needs network and fails because of sandboxing, request approval and rerun it.
3. Inspect the generated commit structure and then inspect commits directly.
   • Use git show --stat --oneline <sha> or equivalent targeted commands.