mcpField
C
changelog-and-release-notes

changelog-and-release-notes

github.com/sylphxaiMarketing & growth153 installsUpdated today
Repository

About changelog-and-release-notes

A skill for turning raw product changes into audience-specific changelogs and release notes. It separates public, technical, store, and support content while highlighting user impact, required actions, compatibility, and rollout details.

Key features

  1. 01Identify audience and release risk
  2. 02Translate changes into user impact
  3. 03Separate notes by channel
  4. 04Surface breaking changes and actions
  5. 05Validate final release notes

Use cases

  1. 01Prepare public release announcements
  2. 02Create technical and support changelogs
  3. 03Explain migrations or compatibility changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill changelog-and-release-notes

After installing, type/changelog-and-release-notesin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/changelog-release-notes-patterns.md

Details

From the project README

Changelog And Release Notes

Use this skill to communicate product change clearly without dumping commits.

Workflow

  1. Identify audience, release type, risk level, channels, and required actions.
  2. Read references/changelog-release-notes-patterns.md.
  3. Convert raw changes into user impact, action needed, compatibility, support, and rollout notes.
  4. Separate public notes, technical changelog, store notes, and internal support notes.
  5. Produce final notes and validation checklist.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not hide breaking changes, migrations, data changes, or pricing/support impacts.
  • Do not expose secrets, internal incident details, or security exploit instructions.
  • Do not write vague notes like bug fixes and improvements when users need specifics.

Output format

Release type:
Audience:
Risk:

Public notes:
- <user-facing change>

Technical/support notes:
- <compatibility, migration, known issue, support macro>

Validation:
- <check>

Comments

Markdown supported