Skip to content
Skills Library
Programming · Writing

developer-release-communication

/developer-release-communication

Use when writing factual release notes or upgrade notices from a release diff or changelog. Not for promotional copy, commits, releases, or publishing.

Licence
Apache-2.0
Last repository change
10.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when writing factual release notes or upgrade notices from a release diff or changelog. Not for promotional copy, commits, releases, or publishing.

Original author description

Use when writing factual release notes or upgrade notices from a release diff or changelog. Not for promotional copy, commits, releases, or publishing.

How it works

  1. What you need before you start
  2. From diff to notes
  3. Breaking changes, deprecations, removals, security fixes
  4. Staying honest
  5. What you hand over
Original SKILL.md headings · 30 lines, 356 words
SKILL.md preview
---
name: developer-release-communication
description: 'Use when writing factual release notes or upgrade notices from a release diff or changelog. Not for promotional copy, commits, releases, or publishing.'
---

# Developer release communication

Write the factual record of a release from material the user supplies (a diff, a changelog, or an explicit change list with source links). You draft in chat only: no commits, no releases, no publishing, no sending, and no invented performance results. The notes you produce are the source of truth the user can hand to `release-promotion` for channel-shaped copy; promotion must stay consistent with them, not the other way around.

## What you need before you start

- `changes` (required): the release diff, changelog entry, or supplied change list with source links.
- `audience` (optional): operators, integrators, or end developers affected. When omitted, write for integrators.

If the user asks for notes but supplies no source, stop and ask for one. Never reconstruct changes from memory.

## From diff to notes

1. Extract every change from the supplied material only, keeping each item traceable to a supplied line or link.
2. Sort the items into Added, Changed, Deprecated, Removed, Fixed, Security. Leave out empty sections, and put nothing in the wrong one.
3. Fill in the fields that make each sensitive item actionable (next section), then check the whole set for invention before handing it over.

## Breaking changes, deprecations, removals, security fixes

A breaking change is not finished until it states who breaks and how, plus the migration action with commands or config where applicable. Deprecations carry their timeline and replacement, removals their last-supported version, security fixes their severity and upgrade urgency. Where a required field is genuinely unknown, say so explicitly rather than leaving a silent gap.

## Staying honest

Every claim traces to the diff or a supplied source with a link; every gap is marked as a gap. No performance result, adoption claim, or cause appears unless the supplied material shows it. When the diff is genuinely ambiguous, present both readings with the question for the author instead of picking one silently.

## What you hand over

Factual release notes using the six sections, breaking-change impacts with migration actions, a source link per claim, and a short verification note stating what was checked and what remains unknown.
Files in this package (2)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named developer-release-communication.

Database snapshot: 13.11.2026 · package version 3bcbf8d8a816 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90release-notes
    Write release notes or a CHANGELOG entry from the commits and merged PRs since the last release. Use when asked for "release notes", "update the changelog", "what changed since v1.2", or before tagging a release.
  • 100generate-release-notes
    This skill should be used when the user asks to "generate release notes", "generate changelog", "create release notes", "write changelog", "what changed since last release", "prepare release notes", "update changelog", or "summarize changes from git history". Parses conventional…
  • 100writing-release-notes
    Use when preparing anything that announces a release to the people who consume it — CHANGELOG entries, GitHub release descriptions, version announcements, upgrade or migration guides, or deprecation notices. Triggers include "write the changelog", "release notes for v2.3",…
  • 85release-notes
    Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal.
  • 90dev10x:release-notes
    Generate JTBD-driven release notes from git commits between releases. Playbook-powered workflow with configurable ticket patterns, output targets, and categories. TRIGGER when: preparing a release and need to generate changelog or release notes from commit history. DO NOT…
  • 100release-notes-changelog-communication
    Use this skill when publish user-friendly release notes highlighting new features, bug fixes, and breaking changes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.