$ loading_
Regenerate OpenClaw release changelog sections from Git history before releases.
Based on the provided material, this is a prompt-oriented skill for regenerating release changelogs, with no required secrets and no declared remote endpoints. The associated open-source repository shows very high community adoption, so overall risk appears low; the main practical note is that its instructions may lead a human to run git commands, but the material itself shows no concrete red flags such as overreach or unexplained data exfiltration.
The material explicitly states that no keys or environment variables are required, and the README does not request API tokens, account credentials, or third-party authorization. No clear credential collection, storage, or abuse surface is shown.
The system metadata declares no remote endpoints, and the skill is classified as prompt-only. While the README mentions `git fetch/pull` as normal repository-history workflow steps, the material does not show the skill itself sending user data to unknown or unrelated services.
Per the objective checks, this is a prompt/document-style skill rather than an executable agent or binary tool. The documentation contains example git commands, but the skill is not shown to automatically spawn processes, execute local code, or invoke privileged system capabilities.
The description is focused on rewriting a target `CHANGELOG.md` version section from git history, with context limited to repository commits, PR/issue references, and release-note content. There is no indication of reading unrelated sensitive local directories, system resources, or other excessive data sources.
The source is an open-source GitHub repository with extremely high community adoption (about 377k stars), which is a strong positive trust signal. Although the license is not declared and maintenance status is unknown, those governance gaps do not amount to a concrete high-risk supply-chain red flag based on the current material.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "openclaw-changelog-update" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-changelog-update/SKILL.md 2. Save it as ~/.claude/skills/openclaw-changelog-update/SKILL.md 3. Reload skills and tell me it's ready
Based on the current Git commit history, regenerate the OpenClaw changelog section for the beta release, grouped into new features, fixes, and improvements, while keeping the release note style consistent.
A polished beta release changelog section ready to use in release notes.
Extract key changes from Git history since the last version tag and generate the OpenClaw stable release changelog, highlighting major fixes and compatibility improvements.
A structured changelog summary tailored for a stable release.
Convert this Git commit history into an OpenClaw release changelog section, removing duplicates, merging similar changes, and outputting clear headings and bullet points.
A consistently formatted changelog section with deduplicated and merged updates.
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 @steipete…
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Prepare and verify OpenClaw stable or beta releases and release notes.
Automate web page workflows, login checks, tab handling, and recovery steps.
Manage issues, PRs, logs, releases, and repos with GitHub CLI.
Verify an OpenClaw release is fully published and working across all channels.
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.
Draft OpenClaw release announcements and testing guidance from release evidence.
Deeply review code and fix only small, high-confidence OpenClaw bugs.
Automate OpenClaw nightly releases, branch maintenance, and forward-porting to main.
Find and fix small high-confidence OpenClaw bugs ready to land.
Run or recover OpenClaw macOS signing, notarization, and release promotion.