release-notes-generator

Generate user-facing release notes from Linear, Jira, and GitHub Issues into a .docx file.

142|16|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/amplitude/builder-skills --skill release-notes-generator-amplitude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes-generator
Source: https://github.com/amplitude/builder-skills/tree/main/execution-skills/skills/release-notes-generator
Command: npx skills add https://github.com/amplitude/builder-skills --skill release-notes-generator-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually turning closed tickets into clear, user‑facing release notes is time‑consuming and error‑prone, often mixing internal work with customer‑visible changes.

Core Features & Use Cases

  • Multi‑source ticket ingestion: Pull completed items from Linear, Jira, or GitHub Issues.
  • Smart filtering & grouping: Exclude internal‑only tickets, group remaining items by product area, and summarize changes in plain language.
  • Formatted output: Generate a polished .docx release note saved to a specified Google Drive folder, ready for review or stakeholder distribution.
  • Use case: Before a product launch, run the skill to collect the sprint’s shipped features and automatically produce a release note document for the marketing team.

Quick Start

Generate release notes for the past week from Jira and save them to Google Drive.

Frequently Asked Questions about release-notes-generator

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

FAQPage Schema
How do I automatically generate release notes from Jira tickets?

Generate release notes from Jira tickets by pulling closed issues via API, filtering out internal items, grouping remaining tickets by product area, and saving a formatted .docx file to Google Drive.

Can I create release notes from multiple sources like Linear and GitHub Issues?

Create release notes from multiple sources by ingesting completed tickets simultaneously from Linear, GitHub Issues, and Jira, then grouping the combined items by product area into a single formatted document.

Do I need Google Drive API permissions to export release notes as a docx file?

Exporting release notes as a .docx file requires Google Drive write permissions to save the document to a designated folder, alongside ticket API access to pull completed issues from your project management platform.

What is the best way to group finished tickets by product area for documentation?

The best way to group finished tickets by product area for documentation is to filter out internal-only work and summarize the remaining user-facing changes in plain language before generating the formatted notes.

How to exclude internal-only tickets when generating user-facing release notes?

Exclude internal-only tickets when generating release notes by applying smart filtering during ticket ingestion to separate internal work from customer-visible changes, ensuring only relevant updates are summarized.