From 87e92c71a4386718436946475b3f2a01dfa70a44 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sat, 25 Apr 2026 09:16:12 +0100 Subject: [PATCH] docs(release): require changelog rewrite from commits --- .agents/skills/openclaw-release-maintainer/SKILL.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.agents/skills/openclaw-release-maintainer/SKILL.md b/.agents/skills/openclaw-release-maintainer/SKILL.md index 1c11e0b10b6..54f334fdddb 100644 --- a/.agents/skills/openclaw-release-maintainer/SKILL.md +++ b/.agents/skills/openclaw-release-maintainer/SKILL.md @@ -97,6 +97,11 @@ Use this skill for release and publish-time workflow. Keep ordinary development ## Build changelog-backed release notes +- Before release branching or tagging, rewrite the target `CHANGELOG.md` + section from commit history, not just from existing notes: scan commits since + the last reachable release tag, add missed user-facing changes, dedupe + overlapping entries, and sort each section from most to least interesting for + users. - Changelog entries should be user-facing, not internal release-process notes. - GitHub release and prerelease bodies must use the full matching `CHANGELOG.md` version section, not highlights or an excerpt. When creating