Backend API Versioning
Use when the user asks about API versioning, URI vs header versioning, breaking changes, deprecating or sunsetting an endpoint, Deprecation and Sunset headers or API migration. Produces a versioning and deprecation plan. Not for API product strategy (use api-product-management).
Install
npx skills add j4flmao/agent-skills --skill backend-api-versioninggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/api-versioning ~/.claude/skills/backend-api-versioningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend API Versioning
## Purpose
Manage API version transitions without breaking existing clients. Support coexistence of multiple API versions and provide clear deprecation signals.
## Agent Protocol
### Trigger
Exact user phrases: "API versioning", "version strategy", "URI versioning", "header versioning", "content negotiation", "accept header", "breaking change", "API migration", "deprecate endpoint", "sunset endpoint", "version path".
### Input Context
- Current API version and clients.
- Type of breaking change being introduced.
- Number of active consumers and their upgrade cadence.
### Output Artifact
Versioning strategy recommendation or configuration. No file unless requested.
### Response Format
```
Strategy: {URI|Header|Content-negotiation}
Current Version: {v1|v2}
Deprecation Policy: {N versions back|N months}
```
### Completion Criteria
- [ ] Versioning strategy chosen and documented
- [ ] Current version endpoints are stable
- [ ] Deprecation headers present on old versions
- [ ] Sunset date communicated via header or docs
- [ ] Migration path documented for consumers
## Architecture Decision Trees
### Versioning Strategy Decision TreeDetails
- Skill name
backend-api-versioning- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/api-versioning/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend API Versioning skill do?
Use when the user asks about API versioning, URI vs header versioning, breaking changes, deprecating or sunsetting an endpoint, Deprecation and Sunset headers or API migration. Produces a versioning and deprecation plan. Not for API product strategy (use api-product-management).
How do I install the Backend API Versioning skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-api-versioning. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend API Versioning popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend Audit Logging
45j4flmao/agent-skills
Use when the user asks about audit logs, audit trail, who changed what, tamper-evident or append-only logs, hash chains, SOC 2 audit evidence or change tracking tables. Produces an immutable audit trail design and code. Not for application logs (use backend-structured-logging).
Backend API Response
45j4flmao/agent-skills
Use when the user asks about API response format, ApiResponse<T> envelope, error codes, Problem Details (RFC 9457), validation error responses or pagination envelopes. Produces a uniform success/error response contract. Not for endpoint and URL design (use backend-api-design).
Backend Auth Patterns
45j4flmao/agent-skills
Use when the user asks about authentication, JWT login with refresh tokens, sessions, OAuth 2.0 / OIDC login, password hashing, MFA, passwordless or refresh token rotation. Produces server-side auth flows. Not for roles and permissions (use backend-authorization) or browser login UI (use frontend-authentication).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.