generate-release-notes

Generate release notes from commits and pull requests via GitHub API.

18.5k|961|Updated Jan 22, 2017
One-click install
npx skills add https://github.com/teambit/bit --skill generate-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-release-notes
Source: https://github.com/teambit/bit/tree/main/.claude/skills/generate-release-notes
Command: npx skills add https://github.com/teambit/bit --skill generate-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of release notes from Git commits and pull requests, simplifying release documentation and reducing manual workload.

Core Features & Use Cases

  • Automated changelog generation: Compile concise notes from commit messages and PR metadata.
  • Versioning support: Create notes for new releases and updated documentation.
  • Documentation-ready output: Write results to releases-docs for further formatting and archiving.

Quick Start

Use the generate-release-notes skill to create a release notes draft from the latest commits and pull requests. The output is stored under releases-docs/releases/ (e.g., new-release.md or v{VERSION}.md).

Frequently Asked Questions about generate-release-notes

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

FAQPage Schema
How do I automate release notes generation from git commits and pull requests?

Automating release notes generation from git commits and pull requests involves collecting commit data via the GitHub API, filtering and categorizing changes, and formatting the results into a structured document stored under releases-docs.

What is the best way to create a changelog from commit logs for new software releases?

Creating a changelog from commit logs for new software releases is done by applying automated workflows across branches to summarize features and fixes, writing the compiled output into structured markdown files like v{VERSION}.md.

Can I generate release notes across multiple branches for versioned release workflows?

Generating release notes across multiple branches is supported for versioned release workflows, allowing you to extract commit logs and pull request metadata from different branches to compile comprehensive release documentation.

Does automated changelog generation work with GitHub pull requests and commit metadata?

Automated changelog generation works directly with GitHub pull requests and commit metadata by fetching data through the GitHub API, filtering the changes, and formatting release summaries for documentation updates.

Where are the generated release notes and changelog files stored after processing commit data?

Generated release notes and changelog files are stored as documentation-ready output under the releases-docs/releases/ directory, typically formatted as new-release.md or v{VERSION}.md for archiving.