research.deprecation-usage
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.
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
More from coinbase/cds
cds-code
|
10cds-docs
|
6feature-planner
A guided workflow for non-technical contributors (designers, PMs) to describe a feature idea and produce a detailed technical implementation plan for an engineer. Invoke manually with /feature-planner.
3ktlo
Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.
2dev.cds-mobile
USE THIS when asked to work on a new or existing (MOBILE) CDS React component in packages/mobile
2git.repo-manager
Instructions to manage a local cache of GitHub repositories. This would typically done in cases where the user want to perform research/analysis on a repository. Invoke whenever you need to clone a repo that isn't present locally, bring an existing clone up to date, or remove a repo from the cache. This skill handles only the mechanical filesystem/git operations — not research, analysis, or anything about the repo's contents.
2