kalilurrahman/kr-claudiator-skills/api-versioning-strategy
Claude Code and agent skill by kalilurrahman/kr-claudiator-skills
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Design an API versioning strategy that allows evolution without breaking existing clients. Outputs versioning scheme, compatibility rules, migration timeline, and consumer communication plan.
Install
npx vskill@latest install kalilurrahman/kr-claudiator-skills/api-versioning-strategySKILL.md
API Versioning Strategy
API versioning lets you evolve your API without breaking existing clients. The challenge is choosing a versioning approach that is simple to implement, easy for clients to understand, and compatible with your deployment and documentation tooling.
Versioning Approaches
Compatibility Rules
URL Path Versioning Implementation
Version Lifecycle Policy
Anti-Patterns to Avoid
| Anti-Pattern | Problem | Fix | |
|---|---|---|---|
| Breaking changes in existing version | Clients break silently | Never break a published version; create v+1 | |
| Too many active versions | Maintenance burden; confusing for clients | Maximum 2 supported versions at once | |
| No deprecation notice | Clients broken without warning | Minimum 6 months notice with migration guide | |
| Versioning every minor change | Version proliferation | Non-breaking changes in same version | |
| No default version | Old clients break when new version is default | Maintain explicit version routing; no implicit default |
10 Rules
- Never make breaking changes to a published version — create a new version.
- URL path versioning (/v1/, /v2/) is the default choice for public APIs.
- Non-breaking changes (adding optional fields, new endpoints) go in the current version.
- Support at most 2 versions simultaneously — v(n) and v(n-1).
- Deprecation notice minimum 6 months before retirement.
- Retired versions return 410 Gone with a migration guide URL in the body.
- Add
DeprecationandSunsetHTTP headers to deprecated version responses. - Write a migration guide before announcing deprecation — not after.
- Track usage per version — retire only when traffic reaches zero.
- Document the version lifecycle policy publicly — clients need to plan migrations.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking08-api-integration/api-versioning-strategy/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
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/kalilurrahman/kr-claudiator-skills/api-versioning-strategy)