Skill file plugins/agentic-awesome-skills-claude/skills/changelog-updates/SKILL.md in sickn33/agentic-awesome-skills. Read the publisher’s upstream source.
Description could not be read from the source metadata.
Start a fresh conversation. Replace the highlighted placeholders.
Use changelog-updates to draft, without publishing, developer-facing release notes for [product/project and release version], based only on [verified change facts, breaking changes, security-disclosure constraints, and release date]. Use the existing developer-audience context if present; otherwise establish the needed audience context through the documented process. Produce clear categorized entries with developer impact, migration guidance and timelines where applicable, without inventing features, dates, metrics, or audience facts.
Required inputs
[product/project and release version]
[verified change facts, breaking changes, security-disclosure constraints, and release date]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: changelog-updatesdescription: "Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features."risk: criticalsource: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/changelog-updatessource_repo: jonathimer/devmarketing-skillssource_type: communitydate_added: 2026-07-01license: MITlicense_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
Changelogs and Product Updates Developers Care About
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
Use this skill when you need create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog",...
Release notes are developer communication, not documentation. When done well, they build trust, demonstrate momentum, and turn updates into marketing moments.
Limitations
Use this skill only when the task clearly matches its upstream source and local project context.
Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.