Agent skill · Audited from source
Git.Detect Breaking Changes
skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b
Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: Analyzes the previous N commits for breaking changes across the CDS public API surface. Use this skill when you need to check if any recent changes will cause breaking changes in the CDS public API surface.
Cite
Cite this page
ModelsAtlas. “Git.Detect Breaking Changes (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/git-detect-breaking-changes
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills/git.resolve-version-conflicts
.claude/skills/git.resolve-version-conflicts
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/skill-creator
.claude/skills/skill-creator
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercoinbase GitHub organizationOwner of the repository this skill is read from
- Source foldercoinbase/cds/.claude/skills/git.detect-breaking-changesThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
- Repository statusNot archivedLast push 7 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Analyzes the previous N commits for breaking changes across the CDS public API surface. Use this skill when you need to check if any recent changes will cause breaking changes in the CDS public API surface.
--- name: git.detect-breaking-changes description: Analyzes the previous N commits for breaking changes across the CDS public API surface. Use this skill when you need to check if any recent changes will cause breaking changes in the CDS public API surface. allowed-tools: Bash(git log:*), Bash(git show:*), Bash(git diff:*), Bash(git rev-parse:*), Read, Glob, Grep argument-hint: [Number of commits to review] model: opus --- ## 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/` ## 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. ## How to analyze 1. Use `git log --oneline -$ARGUMENTS -- <package-path>` for each package to identify relevant commits. 2. Use `git diff HEAD~$ARGUMENTS..HEAD -- <package-path>` and `git show <sha>` to inspect the actual changes. 3. For each changed file, determine if it is reachable from a public export path. If not, skip it. 4. For files that are part of the public API, classify each change using the categories below. ## Breaking change categories ### 1. Removal A previously exported symbol (component, function, hook, type, interface, constant, enum) has been deleted or is no longer exported. Examples: - A component is removed from the barrel export - A named export is deleted - A type or interface is no longer re-exported ### 2. API change (props / function signature) The call signature of a public function, hook, or component has changed in a way that would break existing consumers. Examples: - A required prop is added to a component - A prop is renamed - A prop's accepted values are narrowed (e.g., union type member removed) - A function parameter is removed, reordered, or made required - A hook's return type changes shape - Default values are removed or changed in a way that alters behavior ### 3. Type definition change A publicly exported type, interface, or enum has been modified in a way that would cause consumer TypeScript compilation to fail. Examples: - A property is removed from an exported interface - A type union is narrowed - An enum member is removed or renamed - Generic type parameters are added, removed, or reordered - A type is changed from a type alias to an interface (or vice versa) in a way that breaks assignability ### 4. Visual / layout change A change to styles, spacing, sizing, or visual output that would shift the consumer's application layout or appearance without any API-level change. Examples: - Default margin, padding, or gap values changed - Component dimensions (width, height, min/max) changed - CSS display, position, or flex properties changed - Default visual variants or theme token mappings changed - Border, border-radius, or shadow values changed - Font size, line height, or font weight defaults changed ### 5. DOM / element structure change (web packages only) Applies to `packages/web/` only. Changes to the rendered HTML element tree that could break consumer CSS selectors or DOM queries targeting internal component structure. Examples: - Wrapper elements added or removed - Element tag names changed (e.g., `div` -> `section`) - Nesting order of child elements changed - CSS class names or data attributes on internal elements removed or renamed - `role` or `aria-*` attributes removed or changed ### 6. Behavioral change A change in runtime behavior that could break consumer expectations even though the API signature remains the same. Examples: - Event handler calling conventions changed (e.g., different event object shape) - State management or controlled/uncontrolled behavior changed - Animation or transition behavior changed - Focus management behavior changed - Accessibility behavior changed (e.g., keyboard navigation patterns) ## Output format Organize findings by package. Within each package, group by category. For each breaking change, include: - **Entity**: The name of the affected component, type, function, hook, etc. - **Category**: One of the categories above - **Description**: A concise explanation of what changed and why it is breaking - **File**: The file path where the change occurred - **Commit**: The commit SHA that introduced the change Use this structure: --- ### `packages/<package-name>/` #### Removals | Entity | Description | File | Commit | | ------ | ----------- | ---- | ------ | | ... | ... | ... | ... | #### API Changes | Entity | Description | File | Commit | | ------ | ----------- | ---- | ------ | | ... | ... | ... | ... | _(Continue for each category that has findings. Omit empty categories.)_ --- _(Repeat for each package that has breaking changes. Omit packages with no breaking changes.)_ ## Summary After the per-package breakdown, provide a brief summary section: 1. **Total breaking changes** by category across all packages 2. **Highest-risk changes**: call out the changes most likely to cause widespread consumer breakage 3. **Migration notes**: brief guidance on what consumers would need to do to adapt to each breaking change ## Important guidelines - Be thorough but precise. Do not flag internal refactors that do not affect the public API. - When in doubt about whether something is publicly exported, trace the export chain from `package.json` exports -> barrel files -> source modules. - For visual/layout changes, note the before and after values when possible. - For DOM
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit a03fbe3
git clone https://github.com/coinbase/cds git -C cds checkout a03fbe3db14b
The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- !CAUTION B 89 / 100
first audit · source
a03fbe3db14b
Similar skills
mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Questions about Git.Detect Breaking Changes
What does the Git.Detect Breaking Changes skill do?
Is Git.Detect Breaking Changes safe to install?
What can Git.Detect Breaking Changes access on my machine?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/.claude/skills/git.detect-br — the audited source at commit a03fbe3db14b and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Git.Detect Breaking Changes skill do?
- Is Git.Detect Breaking Changes safe to install?
- What can Git.Detect Breaking Changes access on my machine?