api-changelog-versioning — Claude Code skill: setup and usage
Builds structured API changelogs, deprecation timelines, and step-by-step upgrade instructions for API consumers.
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a claude-codeWhat api-changelog-versioning does
This skill formats API documentation when releases change existing contracts. It groups updates into breaking changes, migration steps, and new features. Breaking updates include explicit before-and-after JSON payloads. Consumers spot field modifications instantly.
The skill organizes lifecycle schedules into tables. It tracks releases across three phases: Current for active work, Maintenance for bug fixes, and EOL for retired endpoints. The guidance suggests giving a 3 to 6-month deprecation warning. It also favors versioning via URL paths like /api/v1/.
Teams versioning via request headers must adapt the templates manually. The default structure assumes URL paths.
What it helps with
- Draft release notes for breaking API updates
- Write step-by-step upgrade guides with before and after payloads
- Publish version deprecation timelines with explicit maintenance dates
- Document incoming webhooks and request query filters
Example prompts for the agent
- Generate a changelog entry for API v3.0.0 with the new JWT auth requirement
- Write a migration guide showing how the user payload changed between v2 and v3
- Create a version support schedule showing when v1 reaches EOL
How to install api-changelog-versioning
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a claude-code2Manually: put the files in place
~/.claude/skills/api-changelog-versioning/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/api-changelog-versioning/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a codex2Manually: put the files in place
.agents/skills/api-changelog-versioning/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a cursor2Manually: put the files in place
.cursor/skills/api-changelog-versioning/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install secondsky/claude-skills api-changelog-versioning2Manually: put the files in place
.github/skills/api-changelog-versioning/SKILL.md1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a gemini-cli2Platform CLI
gemini skills install https://github.com/secondsky/claude-skills --path plugins/api-changelog-versioning/skills/api-changelog-versioningManually: put the files in place
.devin/skills/api-changelog-versioning/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill api-changelog-versioning -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about api-changelog-versioning
How do I install api-changelog-versioning in Claude Code?
Run npx skills add secondsky/claude-skills --skill api-changelog-versioning -a claude-code in your terminal. You can also place the skill file into ~/.claude/skills/api-changelog-versioning/SKILL.md directly.
What does api-changelog-versioning do?
It provides templates for breaking change announcements, deprecation tables, and API upgrade guides. You get structured Markdown outputs with side-by-side payload examples and release timelines.
What version lifecycle stages does this skill define?
The skill defines three stages: Current for active features, Maintenance for bug fixes and security patches, and EOL for retired versions removed from public docs.
Source text
SKILL.md · MIT
---
name: api-changelog-versioning
description: 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.
license: MIT
---
# API Changelog & Versioning
Document API changes with clear migration paths and deprecation timelines.
## Changelog Structure
```markdown
# API Changelog
## v3.0.0 (2025-01-15) - Breaking Changes
### Breaking Changes
- Response format now follows JSON:API specification
- Authentication switched from API tokens to JWT Bearer
### Migration Steps
1. Update base URL to `/api/v3`
2. Replace `Authorization: Token xxx` with `Authorization: Bearer xxx`
3. Update response parsing for new envelope format
## v2.5.0 (2024-12-01) - Features
### New Features
- Webhook support for order events
- Batch operations endpoint
- Field filtering via `?fields=` parameter
### Improvements
- 56% faster response times on /products
- Enhanced error messages with field-specific suggestions
```
## Deprecation Schedule
| Version | Status | Support Until |
|---------|--------|---------------|
| v3.x | Current | Full support |
| v2.x | Maintenance | 2025-06-01 |
| v1.x | EOL | Unsupported |
## Version Support Policy
- **Current**: Full support, new features
- **Maintenance**: Bug fixes and security only
- **EOL**: No support, remove from docs
## Migration Guide Template
```markdown
## Migrating from v2 to v3
### Before (v2)
```json
{ "user_name": "john" }
```
### After (v3)
```json
{ "data": { "type": "user", "attributes": { "name": "john" } } }
```
### Steps
1. Update SDK to v3.x
2. Modify response handlers
3. Test in staging environment
4. Update production
```
## Best Practices
- Provide 3-6 months deprecation notice
- Include before/after code examples
- Mark breaking changes prominently
- Maintain backward compatibility when feasible
- Version via URL path (`/api/v1/`) for clarity
© secondsky · MIT · secondsky/claude-skills