api-deprecation-checker

Detect deprecated API usage across C#, Java, Python, C/C++, TypeScript, and SQL codebases.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill api-deprecation-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-deprecation-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/devex/api-deprecation-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill api-deprecation-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical problem of teams missing deprecated API, library, and language feature usage, which leads to unexpected outages, breaking changes, and compliance failures when deprecated components are removed without proper warning or migration paths.

Core Features & Use Cases

  • 5-Category Deprecation Defect Detection: Flags missing Sunset headers, past-sunset live endpoints, missing migration guides, removals without deprecation periods, and missing versioning strategies, aligned with RFC 8594 and 9745 standards.
  • Multi-Language Coverage: Includes language-specific best practice checks for C#, Java, Python, C/C++, TypeScript, and SQL, with safe vs bad code examples for each.
  • Use Case: Run this Skill during pre-release code reviews to catch deprecation issues before they ship, or during API migration planning to get a full inventory of deprecated endpoints and their required fixes.

Quick Start

Use the api-deprecation-checker skill to audit your project's API surface for deprecation cycle defects and get a prioritized list of required fixes.

Frequently Asked Questions about api-deprecation-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect deprecated API usage across multiple programming languages?

Detect deprecated API usage across C#, Java, Python, C/C++, TypeScript, and SQL by auditing your codebase for outdated libraries and language features. This flags missing Sunset headers, past-sunset endpoints, and removals without proper deprecation periods.

How do I validate RFC 8594 deprecation header compliance for my APIs?

Validate RFC 8594 deprecation header compliance by checking your API surface for missing Sunset headers and past-sunset live endpoints. This audit ensures your service provides proper warning and migration paths before removing deprecated components.

Can I catch breaking changes from deprecated APIs during pre-release code review?

Catch breaking changes from deprecated APIs during pre-release code review by running a deprecation audit. It flags missing versioning strategies and removals without deprecation periods, preventing unexpected outages and compliance failures before shipping.

What is the best way to inventory deprecated endpoints for API migration planning?

Inventory deprecated endpoints for API migration planning by running a deprecation audit across your codebase. You get a prioritized list of required fixes and a full map of outdated libraries needing migration paths.

Does the deprecation audit check for minimum deprecation windows and OpenAPI marking?

The deprecation audit checks for minimum 6-month deprecation window validation and OpenAPI deprecated operation marking. It ensures your API lifecycle management aligns with RFC 8594, 9745, and OpenAPI standards for safe component removal.

Why do I need a deprecation audit if I already use OpenAPI specifications?

You need a deprecation audit alongside OpenAPI specifications because OpenAPI marks deprecated operations, but the audit validates the actual 6-month deprecation window, detects missing migration guides, and flags past-sunset endpoints still live in your codebase.