changeset

name	changeset
description	Use when the user asks to create, generate, write, or apply a Changesets release note/version bump from current code changes (for example "make a changeset", "add a changeset", "apply changesets", or "version packages").
metadata	{"version":"1.0.0"}

Changeset

Use this skill to create and optionally apply Changesets based on the code changes in the current session.

What this skill does

• Detects what changed in the working tree.
• Maps changed files to affected packages in a monorepo or single-package repo.
• Proposes appropriate semver bump levels (patch, minor, major) with rationale.
• Creates a changeset markdown file in .changeset/.
• Applies pending changesets (changeset version) when requested.

Preconditions

• Repository uses @changesets/cli (or has an equivalent changeset script).
• .changeset/ exists or can be created.
• The user requested changeset creation and/or application.

Safety rules

1. Do not apply changesets unless the user asked to apply them.
2. Do not invent package names; only use workspace package names found in package.json files.
3. Exclude private/internal packages unless the repo convention explicitly versions them.
4. If bump type is ambiguous, default to patch and explain why.
5. Never include unrelated files or speculative release notes.