Change Agent Skill

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

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

3 sections, as written by the author

Create a Beachball Change File

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

Steps

Determine the change type:

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

Run the repo's change script to create the change file:

   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>"

Verify the change file was created:

   yarn check:change

Rules

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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

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.