research-deprecation-usage

name

research.deprecation-usage

description

Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools. Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the blast radius of removing a deprecated component or hook, check Sourcegraph for customer usage of deprecated exports, or help the team decide which deprecated APIs are safe to remove in the next major version. Always invoke when asked to "audit deprecated APIs", "check Sourcegraph for deprecated usage", "find usages of deprecated exports", "analyze deprecation impact", or any similar request involving CDS deprecations and customer adoption.

Objective

Your objective is to provide information to user about the extent to which deprecated members of CDS are used in customer repositories. This information should be as accurate as possible as it will be used to inform decisions on whether or not it is safe to drop certain exports in a release or hold them for the next major version.

Removal readiness policy: a deprecated API must remain for one full major version undisturbed before removal. If it was deprecated during major M, it must survive all of M+1; the earliest removal major is M+2 (see @deprecationExpectedRemoval and .claude/skills/deprecate-cds-api/SKILL.md).

Follow the

1 - Determining Research Scope

You may be asked to investigate a single, specific deprecation or all CDS deprecations in general.

If you need to perform a comprehensive audit, there is one additional preparation step:

yarn node scripts/findDeprecations.mjs --json

This script extracts the deprecations with metadata from all CDS packages in JSON format.

2 - Determining the Type of Deprecation

There are two common categories of deprecations in CDS packages:

1. A single prop of a React component