What problem does it solve?
Reviewing an "Update sdk-internal to" pull request in bitwarden/clients is risky because the SDK's TypeScript surface is not committed anywhere, so breaking changes hide inside published npm tarballs and can cause compile errors or silent runtime data corruption.
Core Features & Use Cases
- Surface Diffing: Reconstructs the TypeScript declaration surface from two published @bitwarden/sdk-internal tarballs and diffs it at member granularity (REMOVED, ADDED, MUTATED).
- Commit Range Analysis: Walks the sdk-internal commit range between versions, classifying each hunk as breaking or safe, including serde attribute and enum wire-value changes.
- Call Site Mapping: Greps the repo for every affected symbol, including blind spots like @ts-strict-ignore files, app spec files, and jest.mock factories.
- Use Case: When a PR bumps @bitwarden/sdk-internal in package.json, run this Skill to produce a structured report of compile-time breaks and runtime considerations, then apply in-scope fixes.
Quick Start
Ask the assistant to evaluate the sdk-internal bump in the current PR against the sibling sdk-internal clone and report any breaking changes.