API Compatibility Review

API Compatibility Review is a Quality skill for Claude Code, published by jpicklyk in task-orchestrator.

206 stars20 forkson jpicklyk/task-orchestratorAdded 2026/09/05Repository updated 2026/08/04

ai-coding-assistantai-developmentai-harnessai-memoryai-toolsclaudeclaude-codeclaude-desktopcontext-persistencedeveloper-toolsharness-engineeringharness-frameworkmcpmcp-servermodel-context-protocoltask-managementvibe-codingworkflow-automation

Install in seconds

Install API Compatibility Review

Copy API Compatibility Review into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/api-compat-review ~/.claude/skills/api-compat-review

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/jpicklyk/task-orchestrator.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .claude/skills/api-compat-review/SKILL.md in jpicklyk/task-orchestrator
Installs to: ~/.claude/skills/api-compat-review
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1662 skills

What API Compatibility Review does

API Compatibility Review assesses changes to MCP tools and REST endpoints separately for compatibility notes. Use it when a change may affect parameter schemas, response shapes, or documentation updates.

API Compatibility Review is cataloged under Quality on DirSkills. API Compatibility Review comes from a repository tagged ai-coding-assistant, ai-development, ai-harness, ai-memory and ai-tools.

Documentation

README

Excerpt

API Compatibility Review Framework

Assess API changes by surface — the MCP tool surface (dynamically re-discovered by clients) and the REST surface (hardcoded clients) have different compatibility models. Do not apply REST-style breaking-change caution to MCP tools, and do not apply MCP's rename-friendliness to REST.

Step 1: Classify the Change

Determine which surface(s) the change touches:

MCP tools — application/tools/ tool definitions, parameterSchema, tool description strings
REST API — interfaces/api/v1/routes/, interfaces/api/v1/dto/Dtos.kt, openapi.yaml

A single change (e.g., a domain model field rename) can touch both surfaces independently — assess each.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about API Compatibility Review

What else does jpicklyk publish alongside API Compatibility Review?
API Compatibility Review is one of 25 skills that DirSkills catalogs from jpicklyk/task-orchestrator, the repository it ships in. Its siblings there include Adopt Project Scope, Batch Complete and Configure Server. Each one is a separate skill with its own page in this directory, installs the same way API Compatibility Review does, and is maintained by jpicklyk in that same repository. The rest of the collection is listed on the jpicklyk/task-orchestrator page.
How does API Compatibility Review compare to other Quality skills?
API Compatibility Review ranks #1473 by stars among the 1662 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of API Compatibility Review against them. Open each page to compare what they document and how they install.