Changelog

Translate a clearly defined change range into truthful release communication. Let the amount and importance of shipped work determine the item count, technical depth, and visual format.

Establish scope

Infer from the request and repository:

• target branch, tag range, release, or date window;
• whether uncommitted or unreleased work is excluded;
• audience and expected technical depth;
• output: prose, Markdown, HTML card, image, or a combination;
• existing changelog policy, template, visual system, and prior examples.

Ask only when the range or release status remains ambiguous. Record the exact range in the handoff. Do not describe merged, committed, or feature-flagged work as live without deployment evidence.

Inspect what changed

Start with repository-native release tooling when present. Otherwise inspect the chosen range: