generate-release-notes

Automate release note creation from GitHub, Linear, and Jira data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Perryong/knowledge-agent --skill generate-release-notes-perryong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-release-notes
Source: https://github.com/Perryong/knowledge-agent/tree/main/.claude/skills/generate-release-notes
Command: npx skills add https://github.com/Perryong/knowledge-agent --skill generate-release-notes-perryong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, linear, jira, confluence, notion, hackmd, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of efficiently generating release notes by automating the process of collecting data from various sources, categorizing changes, and organizing them into comprehensive release notes.

Core Features & Use Cases

  • Multi-source Data Collection: Automatically gather information from GitHub, Linear, Jira, and manual inputs.
  • Categorization & Organization: Organize changes into categories like breaking changes, new features, bug fixes, and more.
  • Flexible Publishing: Offers optional publishing to platforms like GitHub, Confluence, Notion, and HackMD.
  • Use Case: After completing a project or sprint, quickly generate a professional release note for stakeholders or team members with minimal manual intervention.

Quick Start

To generate release notes for a specific version, run /generate-release-notes --version <version> --date-range <start_date>-<end_date> --project <project_name>.

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 note generation from GitHub and Jira?

You can automate release note generation by configuring the Skill to collect data from GitHub and Jira, categorize changes into features or bug fixes, and organize them into comprehensive notes. It requires specifying a version, date range, and project name to pull the relevant data.

What is the best way to categorize breaking changes and bug fixes in release notes?

Categorizing breaking changes and bug fixes in release notes is handled automatically by organizing pulled data from integrated sources into structured categories. This ensures stakeholders can quickly identify the nature and impact of recent software changes without manual sorting.

Can I publish release notes directly to Confluence or Notion?

Yes, you can publish release notes directly to Confluence or Notion. The Skill offers flexible publishing options that push the generated documentation to platforms like Confluence, Notion, HackMD, and GitHub immediately after categorization is complete.

Does this release management Skill work with Linear for change tracking?

Yes, the Skill works with Linear for change tracking. It supports multi-source data collection from Linear, GitHub, and Jira, allowing software development teams to automatically gather project changes and integrate them into the final release documentation.

How do I generate release notes for a specific version and date range?

To generate release notes for a specific version, run the command with the desired version number, date range, and project name. The Skill then queries your connected data sources within that timeframe to compile the categorized project reporting output.