git.detect-breaking-changes
Your task
Analyze the previous $ARGUMENTS commits for breaking changes across the CDS public API surface.
Scope
Only analyze changes within these packages:
packages/web/packages/mobile/packages/common/packages/web-visualization/packages/mobile-visualization/
Determining the public API surface
Each package is fully ESM. Inspect each package's package.json "exports" map to determine the public entry points. Every symbol (component, function, hook, constant, type, interface, enum) that is reachable through these export paths is part of the public API and subject to breaking change analysis.
Follow the export chain: package.json exports -> entry index.ts barrel file -> re-exported modules. Any symbol that a consumer could import via the package's published entry points is in scope.
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