changesets

Use when: adding changesets to pull requests, determining semver bump types, versioning packages, or preparing releases. Covers changeset file format, semver guidance, when changesets are required, and the release pipeline.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 concise, actionable reference that gives Claude exactly what is needed to author and classify changesets, with a clearly sequenced release pipeline and one-level-deep pointers to deeper docs. Minor tightening is possible around the example contrast and relocating the semver table to the referenced versioning doc.

Suggestions

Move the full patch/minor/major bullet tables to `contributor-docs/versioning.md` and keep only a one-line summary plus the link in SKILL.md to sharpen progressive disclosure.

Trim the 'Avoid' verbose example to 1–2 lines; the contrast is already clear from the 'Good' example and the surrounding rules.

Add an explicit checkpoint step in the manual-creation flow prompting verification of the bump type against the versioning reference before committing.

Dimension	Reasoning	Score
Conciseness	Lean and mostly efficient with no padding of concepts Claude already knows; the good/avoid example pair is slightly long but earns its place by illustrating the terse-vs-verbose distinction.	4 / 5
Actionability	Provides copy-paste-ready changeset markdown examples, the concrete `npx changeset` command, manual file-creation steps, and explicit semver bump categories with concrete type examples covering the common cases.	5 / 5
Workflow Clarity	The release pipeline is sequenced clearly (PR → changeset-bot → Version Packages PR → publish) and creation options are enumerated; this is single-action guidance rather than a destructive/batch flow, so the minor absence of an explicit 'verify bump against versioning.md' checkpoint keeps it just below 5.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep pointers to `contributor-docs/versioning.md` and `contributor-docs/CONTRIBUTING.md`; no nested references, though the inlined semver bump table could arguably live in the referenced versioning doc.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, well-structured description that pairs an explicit 'Use when' trigger with a concise capability summary covering the full changeset workflow. Trigger-term coverage is good but could add a couple of common synonyms. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'adding changesets to pull requests, determining semver bump types, versioning packages ... preparing releases' plus 'changeset file format, semver guidance, when changesets are required, and the release pipeline' — with comprehensive coverage of the domain.	5 / 5
Completeness	Explicit 'Use when:' trigger clause is paired with a concrete 'what' summary ('Covers changeset file format, semver guidance, when changesets are required, and the release pipeline'), answering both what and when clearly.	5 / 5
Trigger Term Quality	Natural user-facing terms like 'changesets', 'pull requests', 'semver bump', 'versioning packages', and 'releases' are present, but a few common synonyms (e.g. 'changelog', 'version bump') are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (changeset/release tooling) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: primer/react
Path: .github/skills/changesets/SKILL.md
Commit: b111781

Reviewed: about 24 hours ago

Table of Contents

Discovery Implementation Validation

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.