Using OpenClaw to Automate Release Notes

Release notes are one of those tasks that everyone agrees is important but nobody wants to do. After days or weeks of coding, testing, and fixing, the last thing a developer wants to do is write a polished summary of what changed. The result is predictable: release notes are either skipped entirely, written hastily with entries like "various bug fixes," or copy-pasted from commit messages that only make sense to the person who wrote them.

This matters more than teams realize. Release notes are how your users, your support team, your product managers, and your future selves understand what changed between versions. Good release notes reduce support tickets, set user expectations, and create a searchable history of your product's evolution. Bad or missing release notes mean more "what changed?" Slack messages and more time spelunking through git logs.

OpenClaw skills can automate the entire release notes pipeline — from parsing commits and generating changelogs to bumping versions and crafting release communications for different audiences. This guide covers the best skills and strategies from the OpenClaw Bazaar skills directory.

Commit Parsing

The foundation of automated release notes is structured commit messages. If your commits follow a convention like Conventional Commits, they contain enough information to generate meaningful changelogs automatically. If they do not, you need a skill that can extract meaning from unstructured messages.

commit-parser-pro (9,300 installs)

This skill teaches your agent to parse commit histories and extract structured change information. It supports multiple commit conventions including Conventional Commits (feat:, fix:, chore:), Angular commit format, and Gitmoji. For repositories that do not follow a convention, the skill uses heuristic analysis to categorize commits based on the changed files, commit message content, and PR metadata.

openclaw skill install commit-parser-pro

Here is a practical example. Given a range of commits between two tags:

a1b2c3d feat(auth): add OAuth2 PKCE flow for mobile clients
d4e5f6a fix(payments): handle race condition in concurrent refunds
g7h8i9j chore(deps): update next.js to 15.2
k0l1m2n feat(api): add pagination to /users endpoint
o3p4q5r fix(ui): correct date picker timezone offset
s6t7u8v docs: update API authentication guide
w9x0y1z refactor(orders): extract shipping calculator

The skill teaches your agent to parse these into categorized changes:

### Features
- **auth:** Added OAuth2 PKCE flow for mobile clients
- **api:** Added pagination to /users endpoint

### Bug Fixes
- **payments:** Fixed race condition in concurrent refunds
- **ui:** Corrected date picker timezone offset

### Maintenance
- Updated Next.js to 15.2
- Refactored order shipping calculator

### Documentation
- Updated API authentication guide

pr-based-changelog (6,800 installs)

Some teams find that pull request descriptions contain better context than individual commit messages. This skill teaches your agent to generate changelogs from merged PRs instead of commits. It pulls PR titles, descriptions, labels, and linked issues to create richer changelog entries.

openclaw skill install pr-based-changelog

The PR-based approach is especially useful for squash-merge workflows where individual commits are lost. Instead of a single "Merge PR #247: Add payment retry logic" entry, the agent extracts the PR description to produce a detailed changelog entry that explains what the change does and why it matters.

Changelog Generation

Parsing commits is the input; a polished changelog is the output. The gap between raw commit data and a useful changelog requires grouping, filtering, rewriting, and formatting.

changelog-generator (11,100 installs)

This is the most popular release notes skill on the Bazaar. It takes parsed commit data and produces a formatted changelog following the Keep a Changelog standard or a custom format. The skill handles:

• Grouping changes by category (Added, Changed, Deprecated, Removed, Fixed, Security)
• Filtering out internal changes that users do not care about (dependency bumps, CI config changes, refactoring)
• Rewriting developer-facing commit messages into user-facing descriptions
• Linking entries to PRs, issues, and relevant documentation

The rewriting step is the most valuable. A commit message like fix(payments): handle race condition in concurrent refunds becomes a changelog entry like Fixed an issue where simultaneous refund requests could result in duplicate credits. The first is for developers; the second is for users.

openclaw skill install changelog-generator

The skill also supports multiple changelog formats. It can generate Markdown for GitHub releases, HTML for product blogs, plain text for email newsletters, and structured JSON for programmatic consumption by other tools.

Here is how a full changelog generation looks:

Prompt: "Generate release notes for v2.15.0. The release includes
all commits since the v2.14.0 tag. Format for both GitHub release
and a customer-facing email."

Agent output:

**GitHub Release (v2.15.0):**

## What's New
- OAuth2 PKCE authentication flow for mobile applications
- Pagination support for the Users API endpoint

## Bug Fixes
- Fixed a race condition that could cause duplicate refunds
  when multiple requests were processed simultaneously (#1247)
- Fixed timezone offset in date picker component affecting
  users in non-UTC timezones (#1251)

## Improvements
- Shipping cost calculation is now 40% faster for
  international orders

---

**Customer Email:**

Hi,

We have released version 2.15.0 with improvements to
authentication, API usability, and reliability.

**Mobile Authentication:** You can now use OAuth2 PKCE for
secure authentication in mobile applications, eliminating
the need for client secrets.

**API Pagination:** The /users endpoint now supports cursor-based
pagination, making it easier to work with large user lists.

**Bug Fixes:** We resolved an issue where concurrent refund
requests could result in duplicate credits, and fixed a
timezone-related display issue in the date picker.

breaking-change-detector (4,500 installs)

Breaking changes deserve special attention in release notes. This skill teaches your agent to identify breaking changes from commit messages (looking for BREAKING CHANGE: footers), from API diff analysis (removed endpoints, changed response shapes), and from dependency updates that require consumer changes. Breaking changes are highlighted prominently in the changelog with migration instructions.

Version Bumping

Semantic versioning communicates the nature of changes through version numbers. A patch bump means bug fixes, a minor bump means new features, and a major bump means breaking changes. Getting this right matters for consumers of your software who rely on version numbers to assess upgrade risk.

semver-automation (7,400 installs)

This skill teaches your agent to determine the correct version bump based on the changes in a release. It analyzes parsed commits, identifies the highest-impact change category, and recommends the appropriate version increment.

openclaw skill install semver-automation

The skill handles edge cases that trip up manual versioning:

• A release with both features and bug fixes is a minor bump, not a patch
• A release with a breaking change is always a major bump, regardless of other changes
• Pre-release versions follow their own incrementing rules (2.15.0-beta.1 → 2.15.0-beta.2)
• Monorepos may need independent versioning per package

Beyond recommending the version, the skill teaches your agent to update version numbers across all relevant files — package.json, pyproject.toml, Cargo.toml, changelog headers, documentation references, and Docker image tags. Missing one of these files is a common source of version drift.

release-tag-manager (3,900 installs)

This skill handles the git and GitHub side of releases. It teaches your agent to create git tags with consistent naming, generate GitHub releases with the changelog as the body, attach build artifacts, and manage release branches for projects that maintain multiple release lines.

Release Communication

Different audiences need different levels of detail. Developers want to know what changed technically. Product managers want to know which features shipped. Support teams want to know about bug fixes and behavioral changes. End users want to know how the product improved.

release-comms-generator (5,200 installs)

This skill teaches your agent to generate release communications tailored to multiple audiences from a single set of changes. From one changelog, it produces:

• Developer changelog: Technical details, breaking changes, migration guides
• Product update: Feature highlights, screenshots placeholders, user benefits
• Support brief: Behavioral changes, known issues, FAQ entries for anticipated questions
• Social media posts: Concise announcements for Twitter, LinkedIn, and Discord

openclaw skill install release-comms-generator

The multi-audience approach saves significant time. Instead of one engineer writing the changelog, another writing the blog post, and a third writing the support brief, your agent generates all three from the same source data, ensuring consistency across communications.

migration-guide-generator (4,100 installs)

For major releases with breaking changes, users need a migration guide that tells them exactly what to change. This skill teaches your agent to generate step-by-step migration guides from breaking change data. Each guide includes the old pattern, the new pattern, a code example showing the change, and an explanation of why the change was made.

## Migrating from v2.x to v3.0

### Authentication API Changes

**Before (v2.x):**
\`\`\`typescript
const client = new ApiClient({ apiKey: "sk-..." });
\`\`\`

**After (v3.0):**
\`\`\`typescript
const client = new ApiClient({
  auth: { type: "api-key", key: "sk-..." }
});
\`\`\`

**Why:** The new auth configuration supports multiple authentication
methods (API key, OAuth2, JWT) through a unified interface.

Building a Release Automation Pipeline

The most effective setup chains these skills into an end-to-end release pipeline. Install commit-parser-pro for extracting change data, changelog-generator for producing formatted changelogs, semver-automation for version management, and release-comms-generator for multi-audience communication.

With all four skills installed, your release process becomes a single conversation:

Prompt: "Prepare the release for all changes since v2.14.0."

Agent: Analyzes 47 commits and 23 merged PRs, determines this is
a minor release (new features, no breaking changes), bumps version
to 2.15.0, generates the changelog, creates the GitHub release,
and drafts communications for developers, product, and support.

What used to take an afternoon of tedious work now takes minutes. And because the process is automated, it happens consistently for every release — no more "we forgot to write release notes" or "the changelog hasn't been updated since October."

Teams using these skills report releasing more frequently because the overhead of release documentation has been eliminated. When writing release notes takes five minutes instead of two hours, there is no reason to batch up changes into infrequent mega-releases.

Browse all release automation skills in the OpenClaw Bazaar skills directory to find the right combination for your release workflow and toolchain.

Browse the Skills Directory

Find the right skill for your workflow. The OpenClaw Bazaar skills directory has over 2,300 community-rated skills — searchable, sortable, and free to install.

Browse Skills →

Try a Pre-Built Persona

Don't want to configure everything from scratch? OpenClaw personas come pre-loaded with skills, memory templates, and workflows designed for specific roles. Compare personas →