Make Changes

Overview

Write concise release notes that match this repository's .changes conventions. Use this skill for both new change files and edits to existing unpublished ones.

Workflow

1. Read the package's package.json, existing .changes/ directory if present, and any relevant PR diff or commit range.
2. Check whether an unpublished change file already exists for the same work. If it does, update it in place instead of creating a duplicate note.
3. Choose the bump type from the package version and the user-facing impact.
4. Create packages/<package>/.changes/ on demand if it does not already exist.
5. Write user-facing release notes that describe shipped behavior, APIs, exports, migrations, or upgrade work.
6. Run pnpm changes:preview to verify the rendered changelog output.
7. Run lint or broader validation when the task also touched code, package metadata, docs, or release tooling.

Bump Rules