release-changeset

To generate changeset files from conventional commits, the Skill compares git history against existing `.changeset/` entries to detect uncovered commits and creates new consumer-facing files with the correct semver bump type derived from breaking-change indicators.

Semver bump detection analyzes conventional commit types like `feat` and `fix` alongside breaking-change indicators to infer the correct version increment, automatically applying a major bump for breaking changes, minor for features, and patch for fixes.

You can find uncovered commits by comparing your conventional commits history against existing files in the `.changeset/` directory, identifying user-visible changes that lack the required changeset entries to prevent blocked or inaccurately versioned releases.

The changeset workflow supports delegated release phases where `sdd-archive` triggers detect and generate actions, allowing operation when the repository is already initialized with the `.changeset/` directory structure.

A correct changeset file uses YAML frontmatter to specify the semver bump type and package name, followed by English consumer-perspective phrasing that clearly describes the user-visible changes rather than internal implementation details.

Releases get blocked because user-visible changes in the design-system repository lack appropriate changeset coverage, preventing the release workflow from accurately determining and applying the correct semantic versioning bumps.