CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-detect-breaking-changes

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable skill body: exact git commands, a precise breaking-change taxonomy, and a complete output specification leave no ambiguity about what to do. The workflow is well-sequenced with anti-speculation verification guidance; remaining gains are minor — tightening repeated enumerations, adding a coverage-completeness checkpoint, and considering a reference file for the category details.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no explanations of git or TypeScript basics. Minor trimming is possible: the symbol enumeration "(component, function, hook, constant, type, interface, enum)" and the export-chain tracing guidance each appear 2-3 times across sections.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready commands ("git log --oneline -$ARGUMENTS -- <package-path>", "git diff HEAD~$ARGUMENTS..HEAD -- <package-path>", "git show <sha>"), a concrete six-category classification taxonomy with specific examples, and a fully specified output template covering the common cases.

5 / 5

Workflow Clarity

The sequence is clear: identify commits per package, inspect diffs, filter by public-export reachability, classify, then report via a fixed output format with a summary section. Verification guidance exists ("Do not speculate. Only report changes you can verify from the diff"), but there is no explicit checkpoint confirming every commit discovered in step 1 was covered, which keeps it just below a 5.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers, no nested or buried references, and no bundle files required. At ~150 lines with the six-category taxonomy inline, it sits above the inline-only threshold, so splitting detailed category definitions into a reference file would improve it further.

4 / 5

Total

17

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly communicates a well-scoped, niche capability with an explicit 'Use this skill when...' clause, so both what and when are answered. Its main weaknesses are a single concrete action, a circular when-clause that adds no independent trigger contexts, and missing natural synonyms like 'API compatibility' or 'backward incompatible'.

Suggestions

Rewrite the when-clause to give independent trigger contexts instead of restating the what, e.g. "Use when preparing a release, bumping a package version, or when the user asks whether recent commits broke the public API."

Add natural synonym trigger terms such as "API compatibility", "backward incompatible", or "semver / major version" so users phrasing the need differently still match.

Mention one or two more concrete actions (e.g. classifying changes by category and generating migration notes) to strengthen capability coverage beyond the single 'analyzes' verb.

DimensionReasoningScore

Specificity

"Analyzes the previous N commits for breaking changes across the CDS public API surface" names the domain and a single concrete action. Only one action verb is offered, matching 'names domain and 1-2 concrete actions' rather than the several specific actions required for 4.

3 / 5

Completeness

Both the what ("Analyzes the previous N commits for breaking changes...") and the when ("Use this skill when you need to check if any recent changes will cause breaking changes...") are explicitly stated. The when-clause is circular — it restates the what rather than providing independent trigger contexts, so it is not fully concrete as a 5 requires.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "commits", "breaking changes", "recent changes", "public API". Missing common variations such as "API compatibility", "backward incompatible", or "semver", which prevents a 5.

4 / 5

Distinctiveness Conflict Risk

"CDS public API surface" and "breaking changes" in "the previous N commits" define a clear niche tied to a specific codebase's API surface, with distinct triggers and minimal conflict risk with generic skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

coinbase/cds

Path

.claude/skills/git-detect-breaking-changes/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.