release-notes

Analyze commits and generate release objects with translations for staging-to-production releases.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/hubeiqiao/skills --skill release-notes-hubeiqiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/hubeiqiao/skills/tree/main/release-notes
Command: npx skills add https://github.com/hubeiqiao/skills --skill release-notes-hubeiqiao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of preparing and releasing software updates, from analyzing code changes to generating release notes and creating pull requests.

Core Features & Use Cases

  • Commit Analysis: Identifies user-facing changes between staging and main branches.
  • Automated Classification: Classifies changes into feature, improvement, fix, or breaking categories.
  • Version Bumping: Suggests and applies semantic versioning bumps.
  • Release Object Generation: Creates a structured release object with English and translated notes.
  • PR & Tagging Guidance: Guides through the creation of pull requests and GitHub releases.
  • Use Case: Streamline your development cycle by automating the tedious and error-prone task of preparing release notes and managing the release process.

Quick Start

Use the release-notes skill to prepare a release from staging to main.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I automate release notes generation from staging to production?

To automate release notes generation, this Skill analyzes commits between staging and main branches to classify user-facing changes, suggest semver bumps, and generate structured release objects with translated notes.

How does semantic versioning bumping work for automated releases?

Semantic versioning bumps are suggested by analyzing classified commit changes between staging and main, determining whether a feature, improvement, fix, or breaking change requires a major, minor, or patch version increment.

Can I automatically classify commits into features, fixes, and breaking changes?

Yes, automated classification identifies and categorizes user-facing changes from your commits into feature, improvement, fix, or breaking categories to streamline release preparation and note generation.

What is the best way to guide pull request creation and tagging for GitHub releases?

The best way to guide PR creation and tagging is to use a workflow that analyzes code changes, generates a structured release object, and provides step-by-step guidance for creating pull requests and GitHub releases.

Do I need any specific dependencies to automate my staging-to-main release workflow?

No specific dependencies are required to automate your staging-to-main release workflow, as this Skill operates independently to analyze commits, suggest semver bumps, and guide PR creation.

Can I generate release notes with translations for automated workflows?

Yes, you can generate release notes with translations by creating a structured release object that includes both English and translated notes based on the classified user-facing changes.