Agent skill · software engineering · steipete
openclaw-changelog-update
Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.
Why this skill is useful
Adds an executable script for generating and verifying changelog sections from git history, which is not commonly found in public documentation.
What it needs
Requires node installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Changelog Update Use this for changelog rewrites and GitHub release-note source text. For regular beta/stable, prepare complete notes before final-source qualification when possible; Code SHA may then also be Release SHA. Editorial work may overlap Code validation. Do not rerun it per validation-recovery backport; when backports replace the Code SHA, rerun it once after the final Code SHA is green, as a genuine CHANGELOG-only descendant under the existing product-evidence reuse policy (timing). For extended-stable, run it before final exact-head validation and tagging. Do not rerun it for tooling retries, resumed publication, or promotion. Use it with release-openclaw-maintainer; this skill owns changelog content, ordering, grouping, and attribution discipline. Goal Rebuild the target CHANGELOG/<version>.md release section from a complete, generated history manifest, not stale draft notes. Produce grouped user-facing release notes sorted by user interest while preserving every relevant issue/PR ref and every verified human Thanks @... attribution. CHANGELOG.md is the generated release index. The shared owner scripts/lib/release-changelog.mjs resolves release sections and contribution records from a working tree or a pinned Git ref, including historical refs that still contain a monolith. Use node scripts/release-changelog.mjs read --version <version> [--ref <sha-or-tag>] for a section, or add --record for its contribution record. A missing split artifact must not fall back to the root index. Historical releases without records gain no invented provenance. Generated CHANGELOG/ files retain exact migrated or mirrored bytes and are excluded from generic formatting, like the root changelog. Validate them through their owner with pnpm changelog:check. Current writes use the split layout. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-changelog-update