release-notes-generator
Install
Pick the surface you use. Plugins run inside Claude Code, which is available in the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the VS Code and JetBrains extensions. The slash commands are identical on every surface.
From inside any Claude Code session — terminal, desktop app, web app, or IDE extension:
-
Add the RBA Skills marketplace (only needed once per machine):
/plugin marketplace add rbaconsulting/rba-skills-plugin -
Install release-notes-generator:
/plugin install release-notes-generator@rba-ai-hub -
Activate it without restarting:
/reload-plugins
Prefer to browse and click? Run /plugin inside Claude Code to open the interactive plugin manager. It looks the same in the desktop app, web app, terminal, and IDE extensions.
-
Open the plugin manager:
/plugin - Press Tab to reach Marketplaces, choose Add, then enter
rbaconsulting/rba-skills-plugin. - Press Tab again to Discover. Search for
release-notes-generator, press Enter, and pick a scope (User, Project, or Local). - Run
/reload-pluginsto activate it.
If you have the Claude Code CLI installed and want to drive it from a normal shell prompt:
$ claude plugin marketplace add rbaconsulting/rba-skills-plugin
$ claude plugin install release-notes-generator@rba-ai-hub The next Claude Code session loads it automatically.
Overview
Release Notes & Changelog Generator
Turn raw commit history, pull requests, and work items into polished, audience-specific release communications — in minutes, not hours.
RBA projects ship across multiple DX platforms (Sitecore, Umbraco, Optimizely, composable frontends) and report to multiple audiences simultaneously: engineers, project managers, clients, and end users. This plugin provides a suite of skills that harvest, categorise, and format release information for every one of those audiences, then publish it to wherever they live — Confluence, Slack, email, or a versioned CHANGELOG.md.
What's inside
| Artifact | Slug | Purpose |
|---|---|---|
| Skill | release-notes-harvest |
Harvest and categorise commits/PRs/work items from Git or Azure DevOps into structured, deduplicated change sets. The prerequisite step for all other skills. |
| Skill | release-notes-developer |
Generate a technical CHANGELOG.md for engineers — semver-aligned, conventional-commit categorised, with breaking changes prominently flagged. |
| Skill | release-notes-client |
Produce a client-facing feature announcement in plain language — benefit-led, no jargon, suitable for a Confluence page, email, or slide deck. |
| Skill | release-notes-pm |
Write a project-manager sprint/release summary with delivery metrics, decision log, risk callouts, and next-sprint commitments. |
| Skill | release-notes-publish |
Publish a ready-to-ship release note document to Confluence, Slack, or generate a formatted email draft — with channel-appropriate formatting. |
| Agent | release-notes-reviewer |
Subagent that proofreads a draft for tone consistency, coverage gaps, jargon leakage into client-facing text, and missing breaking-change callouts. |
| Command | release-notes |
Slash-command router — reads the current Git context, asks which audience to target, and invokes the right skill chain. |
When to use this plugin
- Sprint end / release day — convert the sprint's merged PRs and closed Azure DevOps work items into a Confluence update and a Slack announcement in one command.
- Client milestone delivery — produce a polished feature announcement that highlights business value, not commit SHAs.
- Developer handoff — generate a semver-aligned
CHANGELOG.mdthat engineers and CI/CD pipelines can rely on for dependency reasoning. - Post-release brief — give the PM a structured summary with delivery metrics and open items for the retrospective.
- Audit trail — maintain a versioned, categorised change history across Sitecore, Umbraco, Optimizely, or composable frontend projects.
Typical workflow
1. /release-notes harvest — pull and categorise changes
2. /release-notes developer — CHANGELOG.md for the engineers
3. /release-notes client — client announcement draft
4. /release-notes pm — sprint summary for the PM
5. /release-notes publish confluence — push to the project Confluence space
6. /release-notes publish slack — post digest to #releases channel
Or run the router and answer the prompts:
/release-notes
How to install
claude plugin install release-notes-generator@rba-ai-hub
After installation each skill is available as a direct slash command or through the router:
/release-notes-harvest v1.4.0..HEAD Azure DevOps project=Sitecore-Rebuild
/release-notes-developer
/release-notes-client
/release-notes-pm sprint=42
/release-notes-publish target=confluence space=PROJ page="Release Notes"
Platform adapters
All skills default to Azure DevOps as the work-item source. Pass a source flag or state it naturally to switch:
--source github— queries GitHub PRs and issues viaghCLI--source jira— reads Jira release version via REST API (PAT required)--source git-log— falls back to rawgit logwhen no issue tracker is available
Publishing defaults to Confluence + Slack. Pass --target email to produce an email-ready HTML/Markdown draft instead.
Permissions
Each skill declares its own allowed-tools following least-privilege. No credential directories are accessed directly. Authenticate with az login (Azure DevOps), gh auth login (GitHub), or set CONFLUENCE_API_TOKEN / JIRA_API_TOKEN environment variables before running publish steps.
Bundled artifacts
Skills
- release-notes-client — Produce a polished, plain-language client-facing feature announcement from the harvest change set — benefit-led, jargon-free, suitable for a Confluence page, email update, or slide deck. Strips internal refactors, infrastructure changes, and commit SHAs.
- release-notes-developer — Generate a semver-aligned, conventional-commit categorised CHANGELOG.md for engineers — with breaking changes prominently flagged, security fixes called out, and migration notes auto-drafted. Reads the harvest.json produced by release-notes-harvest.
- release-notes-harvest — Harvest and categorise commits, pull requests, and work items from Git or Azure DevOps into a structured change set — the prerequisite step before generating any audience-specific release note. Outputs a machine-readable JSON manifest and a human-readable summary.
- release-notes-pm — Write a project-manager sprint or release summary — delivery metrics, decision log, risk callouts, open items, and next-sprint commitments — synthesised from the harvest change set and Azure DevOps sprint data. Aimed at PMs, delivery leads, and internal stakeholders.
- release-notes-publish — Publish a ready-to-ship release note document to Confluence, Slack, or generate a formatted email draft — reads from .release-notes/ drafts produced by the rendering skills and posts to the specified target with channel-appropriate formatting.
Agents
- release-notes-reviewer — Proofreads release note drafts for tone consistency, coverage gaps, jargon leakage into client-facing text, missing breaking-change callouts, and factual consistency against the harvest.json change set. Returns structured findings with severity and suggested fix.
Slash Commands
- /release-notes — Router command for the Release Notes & Changelog Generator — reads current Git context, asks which audience and target, and invokes the right skill chain. Run with no arguments for guided mode; pass a subcommand for direct invocation.
Technical details
- Homepage
- https://rba-skills.tylerschroeder.net/plugins/release-notes-generator/
- License
- MIT
- Maturity
- experimental
- Security review
- No security review
- Owners
-
- engineering
- project-management
- Disciplines
- engineering, project-management
- Lifecycle
- communicate
- Tags
- Last updated
- by Tyler Schroeder
- Source
plugins/release-notes-generator/
Edit this plugin's README on GitHub — opens GitHub's web editor. No git knowledge needed.