skills.rest
bossjones
bossjonesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-notes-generator

Generate categorized release notes from Git commits and pull requests.

1|Updated Jan 4, 2026
Search Tags:#release notes#technical communication#Git integration#commit analysis#automated documentation
One-click install
npx skills add https://github.com/bossjones/boss-skills --skill release-notes-generator-bossjones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes-generator
Source: https://github.com/bossjones/boss-skills/tree/main/plugins/boss-dev/agent-harness/skills/release-notes-generator
Command: npx skills add https://github.com/bossjones/boss-skills --skill release-notes-generator-bossjones

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the manual task of generating release notes for software releases, offering a streamlined, automated solution.

Core Features & Use Cases

  • Automated Note Generation: Quickly creates three distinct outputs for different audiences (devs, users, Slack).
  • Categorization & Translation: Categorizes commits into relevant categories and translates technical language for a broader audience.
  • Use Case: With the skill integrated into the release workflow, a developer can run a single command to produce release notes in CHANGES.md format, PR body format, and Slack message format, ensuring a consistent and user-friendly release communication.

Quick Start

Run 'release-notes-generator generate' to generate release notes for the latest release.

Frequently Asked Questions about release-notes-generator

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

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

To generate release notes automatically, you can analyze Git commits and fetch pull request details via the GitHub API. This process categorizes changes and translates technical language into structured CHANGES.md, PR body, and Slack formats.

What's the best way to format Git commit history for a product release?▼

Formatting Git commit history for a product release is best handled by categorizing commits and translating technical language. This approach produces tailored CHANGES.md files, PR body formats, and Slack messages for distinct audiences.

Do I need GitHub CLI and YAML to automate release note generation?▼

Yes, you need the GitHub CLI (gh) for fetching pull request details and YAML for configuration. Git is also required to analyze commits and successfully automate release note generation.

Can I translate technical commit messages into user-friendly release notes?▼

Yes, you can translate technical commit messages into user-friendly release notes. The automated process categorizes technical changes and outputs translated summaries suitable for a broader audience and Slack updates.

Related Skills

Explore More Product & Management Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
i9wa4i9wa4
11

github-pr-operation

Retrieve GitHub PR details and post inline comments via gh CLI.

Community
Advanced
awinogradovawinogradov
5

run

Automate development workflows from planning through pull request monitoring.

Community
Advanced
synqingsynqing
1

changelog-generator

Generate user-facing changelogs from git commits with categorized changes.

Community
Intermediate