GI

git.detect-breaking-changes

Analyzes commits for breaking changes in public API surfaces.

Install

mkdir -p .claude/skills/git-detect-breaking-changes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11962" && unzip -o skill.zip -d .claude/skills/git-detect-breaking-changes && rm skill.zip

Installs to .claude/skills/git-detect-breaking-changes

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

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.
206 chars✓ has a “when” trigger
Advanced

Key capabilities

  • →Analyze commits for breaking changes in CDS public API surface
  • →Identify relevant commits within specified packages
  • →Determine public API surface by inspecting `package.json` 'exports' map
  • →Classify breaking changes into categories like removal, API change, type definition change
  • →Report visual/layout changes and DOM/element structure changes

How it works

The skill uses git commands to inspect a specified number of previous commits within defined packages, determines the public API surface, and classifies changes into breaking categories.

Inputs & outputs

You give it
The number of previous commits to review
You get back
A structured report detailing breaking changes by package and category, including entity, description, file, and commit, along with a summary

When to use git.detect-breaking-changes

  • →Check for breaking API changes
  • →Audit public package exports
  • →Validate interface compatibility

About git.detect-breaking-changes

Examines recent commits to identify breaking changes within public API packages. It inspects package exports to ensure that symbols accessible to consumers remain stable.

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.

When not to use it

  • →When analyzing internal refactors that do not affect the public API
  • →When the analysis needs to speculate on changes not verifiable from the diff
  • →When the scope is outside `packages/web/`, `packages/mobile/`, and `packages/common/`

Limitations

  • →It only analyzes changes within `packages/web/`, `packages/mobile/`, and `packages/common/`.
  • →It does not flag internal refactors that do not affect the public API.
  • →It does not speculate; it only reports changes verifiable from the diff.

How it compares

This skill automates the detection and classification of breaking changes in a public API, providing a structured report, unlike manually reviewing commit histories and diffs.

Compared to similar skills

git.detect-breaking-changes side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git.detect-breaking-changes (this skill)06moReviewAdvanced
github-code-review136moReviewAdvanced
reviewing-code2112moNo flagsIntermediate
reviewing-nextjs-16-patterns1112moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry