skills.rest
dpaola2
dpaola2COMMUNITY
Explore all skills by this author →
Website𝕏@dpaola2GitHub

release-notes

Generate markdown release notes from completed Linear cycle issues.

3|Updated Feb 18, 2026
Search Tags:#automation#development#changelog#release notes#issue tracking#linear
One-click install
npx skills add https://github.com/dpaola2/pipeline-skills --skill release-notes-dpaola2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill release-notes-dpaola2

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of release notes by pulling completed issues from a specified Linear cycle, categorizing them, and formatting them according to a predefined template.

Core Features & Use Cases

  • Automated Issue Aggregation: Gathers completed issues from multiple engineering teams within a Linear cycle.
  • Intelligent Categorization: Sorts issues into "New Features," "Maintenance," and "Cleaning Up" based on labels and title heuristics.
  • Use Case: At the end of a development sprint, use this skill to quickly generate a draft of release notes for the upcoming app update, ensuring all significant changes are captured and presented clearly.

Quick Start

Generate release notes for cycle number 47.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate release notes from a Linear cycle?▼

To generate release notes from a Linear cycle, fetch completed issues, categorize them by labels or title keywords, and format the output into a markdown file using a predefined template.

How does automated changelog categorization work for completed issues?▼

Automated changelog categorization sorts completed Linear issues into "New Features," "Maintenance," and "Cleaning Up" based on specific issue labels and title heuristics, defaulting uncategorized items to maintenance.

Can I aggregate completed issues from multiple engineering teams in Linear?▼

Yes, you can aggregate completed issues from multiple engineering teams within a single Linear cycle, pulling all relevant tasks together to generate comprehensive release notes for the entire sprint.

What is the best way to draft release notes for an app update sprint?▼

The best way to draft app update release notes is to automate issue aggregation from your tracking system, categorize completed work intelligently, and output a formatted markdown draft capturing all significant changes.

Does this release notes generator support manual mobile build version inputs?▼

Yes, the release notes generator prompts for mobile build versions during the formatting process, ensuring the specific build numbers are included alongside the categorized list of completed Linear issues.

Related Skills

Explore More Software Engineering Skills→
breethomasbreethomas
16

issue-audit

Analyze a Linear team's issues to surface organization patterns and conventions.

Community
Intermediate
omeragaakbasomeragaakbas

stakeholder-map

Generate a stakeholder map and communication plan table from project briefs.

Community
Intermediate
lobehublobehub
81.4k

linear

Automate Linear issue status updates and completion comments via MCP tools.

Official
Advanced
cbgbtcbgbt
5

prepare-core-kit-release

Bumps Twoliter.toml version and generates changelog from git history for bottlerocket-core-kit releases.

Community
Intermediate