release-notes-author

Generate release notes from git commits and PRs for a tag range.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill release-notes-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes-author
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/release-notes-author
Command: npx skills add https://github.com/clawperator/clawperator --skill release-notes-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) components.

What problem does it solve?

This skill automates the creation of changelog entries by synthesizing commit data and PR information into user-facing release notes for a given version range, ensuring consistency and traceability.

Core Features & Use Cases

  • Generates changelog entries for a specified start and end tag by aggregating commits and PRs.
  • Groups changes by product surface (Node, Docs, Android) and applies deterministic eligibility rules for inclusion.
  • Produces a structured, human-readable release note format with subjects, bodies, files touched, and PR links.
  • Use cases include releasing new versions of a project with a clear, publishable changelog.

Quick Start

Provide a start tag and end reference to generate a changelog block for that range.

Frequently Asked Questions about release-notes-author

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

FAQPage Schema
How do I generate release notes from git commits for a specific tag range?

Generate release notes by providing a start and end tag, which aggregates git commits and PR data to produce a structured changelog. The skill parses commit subjects and bodies, mapping touched files to organize changes by product surface.

How do I automate changelog creation for Android, Node, and Docs surfaces?

Automate changelog creation by grouping aggregated commit data by Android, Node, and Docs surfaces. Deterministic keep and drop eligibility rules are applied to construct a coherent, publish-ready block with PR links for each surface.

Does generating release notes require gh and git dependencies?

Generating release notes requires both git and gh dependencies to function. The git dependency gathers commit data, while gh fetches PR information to ensure traceability and include PR links in the final user-facing changelog.

What is the best way to produce deterministic changelogs from commit history?

Deterministic changelogs are produced by parsing SUBJECT and BODY fields from commits and applying fixed keep and drop rules. This ensures consistency and traceability across versions by organizing changes and PR links into a structured format.

Why are some git commits dropped from my generated changelog block?

Commits are dropped from the changelog block based on deterministic eligibility rules applied during aggregation. The skill filters the commit data across product surfaces to ensure only relevant changes are included in the final release notes.

Can I use this release notes generator with my existing git repository?

You can use this generator with any git repository that has tagged versions. By specifying a start tag and end reference, the script aggregates the commit history and PR information within that range to output a publish-ready changelog.