jonathimer/devmarketing-skills/changelog-updates
Claude Code and agent skill by jonathimer/devmarketing-skills
- community
Checking that the SKILL.md file is still in the repository.
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", "product updates", "version communication", "breaking changes", "deprecation notice", "what's new", "release communication", "developer updates", "API versioning", "migration announcement"
Install
npx vskill@latest install jonathimer/devmarketing-skills/changelog-updatesSKILL.md
Changelogs and Product Updates Developers Care About
Release notes are developer communication, not documentation. When done well, they build trust, demonstrate momentum, and turn updates into marketing moments.
Overview
Changelogs serve multiple audiences and purposes:
- Active developers: "What changed that affects my integration?"
- Evaluating developers: "Is this product actively maintained?"
- Developer advocates: "What's worth sharing with my audience?"
- Your team: Historical record of what shipped and when
This skill covers creating changelogs that inform, build trust, and occasionally delight.
Before You Start
Review the developer-audience-context skill to understand:
- How do your developers prefer to receive updates?
- What changes do they care most about?
- How much detail do they need?
- What's their tolerance for breaking changes?
Your changelog tone and detail level should match your audience.
Changelog Format
The Standard Structure
Change Categories
| Category | Use For | |
|---|---|---|
| Added | New features, new endpoints, new parameters | |
| Changed | Behavior changes, performance improvements | |
| Deprecated | Features being phased out (still working) | |
| Removed | Features that no longer exist | |
| Fixed | Bug fixes | |
| Security | Security-related changes |
Good vs. Bad Entries
Good Changelog Entries:
Bad Changelog Entries:
Writing Style
Be specific:
Include context:
Link to resources:
Explain impact:
What to Include
Always Include
API Changes:
- New endpoints
- New parameters
- Changed response formats
- Changed error codes
SDK Changes:
- New methods
- Changed method signatures
- New configuration options
Breaking Changes:
- Anything that requires code changes
- Removed features
- Changed defaults
Security Fixes:
- Even if vague, acknowledge security updates
- Follow responsible disclosure timeline
Consider Including
Performance Improvements:
Developer Experience:
Infrastructure:
Skip or Minimize
Internal refactoring:
Minor dependency updates:
Typo fixes:
Versioning Communication
Semantic Versioning Explained to Users
Help developers understand what version numbers mean:
Version Pinning Guidance
Help developers make good choices:
API Versioning Communication
curl https://api.example.com/v2/users
or
curl -H "API-Version: 2024-01-15" https://api.example.com/users
Breaking Changes
Breaking Change Announcement Template
Before (v2.x)
client.old_method(user_id="123")
After (v3.x)
client.new_method(id="123")
Before
POST /v1/users/123/analyze
After
POST /v2/users/123/analyze
Breaking Change Communication Timeline
Deprecation Notices
In-Code Deprecation
API Deprecation Headers
Deprecation Changelog Entry
Building Anticipation
"Coming Soon" Announcements
Build excitement for upcoming features:
Release Cadence Communication
Set expectations:
Feature Launches as Events
Turn significant releases into moments:
Distribution Channels
Where to Publish
| Channel | Audience | Content Level | |
|---|---|---|---|
| GitHub Releases | Developers on repo | Full changelog | |
| Docs changelog | All developers | Full changelog | |
| Blog | Broader audience | Highlights + context | |
| Active users | Summary + action items | ||
| Twitter/X | Community | Highlights only | |
| Discord/Slack | Engaged community | Discussion + highlights |
Email Templates
Regular Release:
Breaking Change:
Tools
Changelog Generation
- Conventional Commits: Structured commit messages
- semantic-release: Automated changelog from commits
- changesets: Monorepo changelog management
- Keep a Changelog: Format specification
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 96 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/changelog-updates/SKILL.md
Popularity
- Repository stars
- 46
- Repository forks
- 2
- 7-day trend score
- 19
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 17 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/jonathimer/devmarketing-skills/changelog-updates)