Change

microsoft/change

Create a beachball change file for the current changes. Determines change type (patch/minor) and generates a description from the diff.

375 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

20188

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/fluentui --skill change

found in the instruction text

Bash runs shell commands — read the instruction before connecting

3 sections, as written by the author

Generate a change file for the current branch's modifications using the repo's beachball setup.

patch — bug fixes, internal refactors, test-only changes
minor — new features, new exports, new component variants
none — changes that don't affect the published package (stories, docs, tests only)
Never use major without explicit user approval

Generate a descriptive message following the format: fix(package-name): description or feat(package-name): description

   yarn change

This runs beachball change --no-commit (configured in root package.json).

Beachball automatically detects which packages need change files.

For non-interactive usage with a specific type and message:

   yarn beachball change --no-commit --type <type> --message "<message>"

   yarn check:change

Always use yarn change or yarn beachball change — never manually create change files
The message should describe the user-facing impact, not the implementation detail

Copy the folder

Take microsoft/change from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.