with one click
openclaw-changelog-update
// Regenerate OpenClaw release changelog sections from git history before beta or stable releases.
// Regenerate OpenClaw release changelog sections from git history before beta or stable releases.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.
Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.
Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.
Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.
| name | openclaw-changelog-update |
| description | Regenerate OpenClaw release changelog sections from git history before beta or stable releases. |
Use this for release changelog rewrites and GitHub release-note source text.
This is mandatory before every beta, beta rerun, stable release, or stable
rerun. Use it with release-openclaw-maintainer; this skill owns changelog
content, ordering, grouping, and attribution discipline.
Rewrite the target CHANGELOG.md version section from history, not from stale
draft notes. Produce grouped user-facing release notes sorted by user interest
while preserving every relevant issue/PR ref and every human Thanks @...
attribution.
YYYY.M.D, without beta suffix.main before branching when possible:
git fetch --tags origingit pull --ff-onlygit status -sbgit log --first-parent --date=iso-strict --pretty=format:'%h%x09%ad%x09%s' <base-tag>..<target-ref>git log --first-parent --grep='(#' --date=short --pretty=format:'%h%x09%ad%x09%s' <base-tag>..<target-ref>--since='24 hours ago' when main moved during the release.## YYYY.M.D## Unreleased section above the target releaseUnreleased contains release-bound notes, fold them into the target
section instead of deleting them### Highlights: 5-8 bullets, broad user wins first### Changes: new capabilities and behavior changes### Fixes: user-facing fixes first, grouped by impact and surface#issue, (#PR), Fixes #..., and Thanks @...Thanks @author, even when the PR had no linked issueFixes #... or referenced bug issue
represented by a user-facing entry needs Thanks @reporter unless the
same handle is already thanked in that bulletCo-authored-by contributor on represented user-facing work
needs Thanks @handle when a GitHub handle is knownThanks @... handles in one bullet are expected; do not drop or
collapse contributor credit just because the note is grouped#NNN refs from the notesCo-authored-byThanks @... set@openclaw, @clawsweeper, or @steipetesrc/plugins/compat/registry.tssrc/commands/doctor/shared/deprecation-compat.tsremoveAfter is on/before release date, resolve it
or explicitly record the blocker before shippinggit diff --checkscripts/committer "docs(changelog): refresh YYYY.M.D notes" CHANGELOG.mdmainIf GitHub API quota is exhausted, do not idle. Continue work that does not need GitHub API:
npm view checksOnly GitHub Release creation, workflow dispatch, run polling, artifact download, and issue/PR mutation need API quota.