api-changelog-versioning
Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.
95
93%
Does it follow best practices?
Impact
98%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
12%Document Breaking API Changes for Payments Service v4.0
Changelog structure & breaking changes
Versioned section header
50%
100%
Breaking Changes subsection
100%
100%
Migration Steps subsection
50%
100%
Before code example
100%
100%
After code example
100%
100%
Response envelope before/after
100%
100%
URL path versioning
100%
100%
Second version section
100%
100%
New Features subsection
80%
100%
Breaking prominence
100%
100%
100%
16%Communicate API Version Lifecycle to Enterprise Customers
Deprecation schedule & support policy
Deprecation table present
100%
100%
Table Version column
100%
100%
Table Status column
100%
100%
Table Support Until column
100%
100%
Current tier used
100%
100%
Maintenance tier used
100%
100%
EOL tier used
100%
100%
Support policy section
100%
100%
3-6 month notice window
0%
100%
EOL no support statement
100%
100%
94%
-1%Write a Developer Migration Guide for GraphQL API Upgrade
Migration guide template
Migration section header
87%
100%
Before section
80%
80%
After section
80%
80%
Before code block
100%
100%
After code block
100%
100%
SDK update step first
100%
100%
Staging environment step
100%
100%
Production step last
100%
83%
URL path versioning in examples
100%
100%
Response handlers step
100%
100%
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.