update-release-notes

Draft and publish categorized release notes to Confluence after PR approval.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/seanwachs/cursor-skills --skill update-release-notes-seanwachs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-release-notes
Source: https://github.com/seanwachs/cursor-skills/tree/main/.agents/skills/update-release-notes
Command: npx skills add https://github.com/seanwachs/cursor-skills --skill update-release-notes-seanwachs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts and publishes release notes for PRs in Confluence, ensuring a consistent format and timely communication to stakeholders.

Core Features & Use Cases

  • Automates creation and updating of Confluence release notes pages after PR approval.
  • Classifies changes into breaking changes, features, bug fixes, and pipeline items using a canonical release-note format.
  • Guides the user through the release notes workflow from discovery to publication, including diff collection and Jira context.

Quick Start

Run this after a PR is approved to draft and publish the release note in Confluence.

Frequently Asked Questions about update-release-notes

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

FAQPage Schema
How do I automate release notes generation in Confluence after a PR is approved?

Automating release notes for Confluence involves taking approved PR diffs and Jira context to draft structured markdown entries. This workflow categorizes changes into breaking changes, features, bug fixes, and pipeline items before publishing.

What is the canonical format for structuring release notes?

The canonical release notes format categorizes changes into specific sections: breaking changes, features, bug fixes, and pipeline items. It leverages existing notes in the Release Notes folder to maintain consistent tone and structure across entries.

Can I use Jira context and PR diffs to document user-facing changes?

Yes, you can use Jira context and PR diffs to describe user-facing changes. The workflow guides you to collect diffs, identify the relevant version, and generate a markdown-formatted release note ready for Confluence.

What's the best way to classify breaking changes and features for release notes?

The best way to classify breaking changes and features is by enforcing a structured workflow from discovery through publication. This process uses PR diffs and Jira context to accurately sort changes into a canonical release note format.

Does the release notes workflow require existing pages in the Confluence Release Notes folder?

The workflow discovers and references existing notes within the Confluence Release Notes folder to ensure consistent tone and structure, but it can draft and publish new markdown-formatted entries independently after PR approval.