draft-changelog-entry

You can draft changelog fragments from PR metadata by reading commit messages and backlog-sweep state to generate a review-ready file at changelog.d/<row-id>.md without modifying the main CHANGELOG.md.

A non-destructive changelog fragment workflow outputs individual files under changelog.d/ for release tooling to consume later, ensuring the main CHANGELOG.md remains unmodified during PR preparation.

Changelog fragments document backlog-sweep initiatives by using the active state.json file to determine the changelogCategory and extracting the commit message body to draft targeted release notes for closed rows.

No, the changelog fragment drafting process does not edit CHANGELOG.md; it only outputs a single fragment file in the changelog.d directory for later consumption by release tooling.

To generate a changelog fragment, you need an initiative id, a commit SHA or branch name, and one or more row-id values to map the PR metadata to the correct changelog category.

Use changelog fragments when preparing a PR for ship or closing backlog-sweep rows, allowing release tooling to aggregate and integrate the isolated changes into CHANGELOG.md later.