openclaw-changelog-update

Rewrite CHANGELOG.md release sections from git history with preserved references.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-changelog-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-changelog-update
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/openclaw-changelog-update
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-changelog-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerate OpenClaw release changelog sections from git history before beta or stable releases, ensuring release notes reflect actual changes, preserve attribution, and maintain audit discipline.

Core Features & Use Cases

  • Rewrites the target CHANGELOG.md sections from git history, ensuring notes are derived from actual commits and PRs rather than drafts.
  • Preserves #issue, (#PR), Fixes #..., and Thanks @author references, and folds any Unreleased notes into the targeted release section.
  • Enforces a stable, user-facing release-note structure with clearly defined sections and consistent formatting for each release.

Quick Start

Use this skill to refresh your project's release notes from the latest mainline history before cutting a new release.

Frequently Asked Questions about openclaw-changelog-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from git history automatically?

Generate release notes from git history by rewriting target CHANGELOG.md sections using actual commits and PRs. This ensures release notes reflect real changes rather than manual drafts, preserving attribution and references.

How do I preserve issue and PR references in my changelog?

Preserve issue and PR references in your changelog by extracting #issue, (#PR), Fixes #..., and Thanks @author tags directly from git history. The notes fold Unreleased entries into the targeted release section automatically.

What is the best way to format release notes for open-source projects?

Format release notes for open-source projects by enforcing a stable, user-facing structure with consistent sections. This approach validates formatting before shipping, ensuring reproducible documentation for each release.

Can I use automated changelog generation for internal releases?

Automated changelog generation supports internal releases by deriving notes from actual mainline git history. It maintains audit discipline and accurate attribution without requiring manual draft compilation.

When do I need to regenerate a changelog before a beta release?

Regenerate a changelog before a beta release when you need to refresh project notes from the latest mainline history. This ensures the release section accurately captures all recent changes and references before cutting the release.