Frb Write Changelog

Use the previous version as the lower bound when deciding which merged PRs belong to the target release.

Step 4: Filter and normalize

Keep all PRs in merged status that belong to the release range.

• Exclude unmerged PRs.
• Exclude PRs outside the release range.
• Do not filter by target branch.
• Keep docs, CI, and chore PRs if they are merged in the range.
• Exclude all-contributors PRs such as docs: add <name> as a contributor for code/doc.

Normalize titles before writing.

• Rewrite noisy internal titles into concise changelog language.
• Avoid duplicate summaries for split or "continued" PRs.
• Preserve repo-specific capitalization such as CI, GitHub, Flutter, Rust, DCO, and V1.

Step 5: Write the section

Match the existing changelog style.

• Write each item as * Summary #1234.
• Append (thanks @username) when attribution is appropriate.
• Keep items in merge order from newest to oldest unless the surrounding section clearly uses another order.

Edit only CHANGELOG.md. Do not manually edit generated files for this task.

Step 6: Review and commit

Review the final diff.

• Confirm the change is limited to the target release section.
• Confirm wording and ordering match nearby release sections.
• Create a small atomic commit after finishing the edit.

Step 7: Verify with a subagent

Launch a separate subagent after finishing the changelog draft.

• Ask the subagent to independently collect the merged PR list for the same release range.
• Ask the subagent to compare that list against CHANGELOG.md.
• Ask the subagent to report missing PRs, suspicious duplicates, and formatting inconsistencies.
• Apply any confirmed fixes, then re-check the final diff.

Step 8: Ask the user to review ordering

Tell the user the changelog draft is complete and ask for a manual review.

• Ask the user to review the wording.
• Ask the user to review the ordering of entries.
• Adjust the ordering if the user wants a different presentation from the mechanically collected order.

Step 9: Re-verify after human edits

Launch a separate subagent after the user finishes manual edits.

• Ask the subagent to independently inspect the final CHANGELOG.md.
• Ask the subagent to compare the final text against the merged PR list for the same release range.
• Ask the subagent to specifically report any missing PR numbers.
• Apply any confirmed fixes, then do one final diff check.