Problem or use case
R06 (specific, not generic, notes) and R07 (release body matches or links the changelog entry) show up as Fail/Partial across wave-1 repos (for example markitdown-mcp's R07). Writing compliant release notes from an existing changelog entry is mostly formatting and cross-referencing, not judgement — a good fit for a writer agent rather than only a reviewer.
Desired outcome
A local, credential-free packages/release-notes-writer package: reads the changelog entry for the version being released and drafts release notes in the shape R06/R07 need (specific content, matching or linking the entry, breaking-change warnings surfaced), for the maintainer or release workflow to use. Builds on templates/release-notes/, which already exists as a static gate script — this is the authoring half, not the gate.
Alternatives and impact
Alternative: rely on the existing release-notes gate template and manual writing. Works, but the gate only checks presence/matching, it doesn't help write a good entry. Affects any repository that publishes releases and has accumulated enough history to be worth automating.
Problem or use case
R06(specific, not generic, notes) andR07(release body matches or links the changelog entry) show up as Fail/Partial across wave-1 repos (for example markitdown-mcp'sR07). Writing compliant release notes from an existing changelog entry is mostly formatting and cross-referencing, not judgement — a good fit for a writer agent rather than only a reviewer.Desired outcome
A local, credential-free
packages/release-notes-writerpackage: reads the changelog entry for the version being released and drafts release notes in the shapeR06/R07need (specific content, matching or linking the entry, breaking-change warnings surfaced), for the maintainer or release workflow to use. Builds ontemplates/release-notes/, which already exists as a static gate script — this is the authoring half, not the gate.Alternatives and impact
Alternative: rely on the existing release-notes gate template and manual writing. Works, but the gate only checks presence/matching, it doesn't help write a good entry. Affects any repository that publishes releases and has accumulated enough history to be worth automating.