release-notes

Draft GitHub release notes from commits between the latest version tag and HEAD.

1|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill release-notes-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/release-notes
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill release-notes-taxmaxi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, product-focused release notes from raw git history is repetitive and error-prone. This Skill turns commits since the last version tag into a structured GitHub Release body that follows the TaxMaxi house style. ## Core Features & Use Cases - Commit-driven drafting: Finds the previous version tag with git describe, inspects commits and diffs since that tag, and summarizes the changes. - House style enforcement: Applies the TaxMaxi release format with sections like "What changed", "Deployment notes", and "Commits since <tag>", plus a longer launch-release shape for first public releases. - Use Case: After merging several pull requests, ask for release notes and receive a ready-to-paste GitHub Release body with short SHAs, deployment notes, and a concise theme summary. ## Quick Start Draft release notes for all commits since the latest version tag using the TaxMaxi release style.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate release notes from git commits?▼

Find the previous version tag with git describe --tags --abbrev=0, list commits with git log --oneline <tag>..HEAD, then summarize them into a structured release body. This Skill automates that workflow following the TaxMaxi house style.

How to write GitHub release notes in a consistent format?▼

Use a fixed structure: a short theme paragraph, a "What changed" section, "Deployment notes", and a "Commits since <tag>" list with short SHAs. This Skill enforces that structure and avoids generic categories like Features and Fixes.

Does this Skill create or publish the GitHub Release?▼

No. It only drafts the release body text. Creating, editing, or publishing a GitHub Release happens only when the user explicitly asks for it.

What happens if there are no commits since the last tag?▼

The Skill reports that there is nothing to release instead of fabricating notes. It checks the commit range between the latest version tag and HEAD before drafting anything.

When should the longer launch release format be used?▼

Use the longer launch shape only for a first public release or a major product announcement, matching the v0.1.0-beta.1 style. Normal and beta releases use the shorter default structure.