Create a changelog from reviewed commits

Commit messages are clues about implementation, not a complete account of user impact. Combine them with the approved release scope.

Use a reviewable project copy

Give the product or code teammate the relevant specification and a dedicated project folder or branch. Separate a proposed change from permission to release it. Request a diff or evidence table alongside the recommendation, and run checks that exercise the behavior in question. Generated code and test output still need review in the actual project environment.

Inputs for this workflow: Reviewed commit list, pull-request descriptions and release boundaries.

Work through the task

1. Identify user-visible changes.
2. Exclude work outside the intended release.

A brief you can adapt

Draft changelog.md with Added, Changed and Fixed sections, linking each item to its source change. Flag ambiguous behavior for review.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Verify each entry against the actual diff or reviewer notes and check whether it has shipped.

Where this approach can fail

Do not include a planned change solely because a branch or issue mentions it.

For the related desktop setup, see local folder.