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. Read recent released entries from the relevant package changelog on origin/main. Use them as the editorial reference for voice, structure, and level of detail; use unpublished change files to detect overlap and follow placement conventions, not as the sole writing model.
3. 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.
4. Choose the bump type from the package version and the user-facing impact.
5. Create packages/<package>/.changes/ on demand if it does not already exist.
6. Write changelog copy that describes shipped behavior, APIs, exports, migrations, or upgrade work from the user's perspective.
7. Run pnpm changes:preview and review the affected package sections as complete changelog sections, not isolated rendered files. Edit for repetition, inconsistent voice, fragmented migrations, and overlapping notes.
8. Run lint or broader validation when the task also touched code, package metadata, docs, or release tooling.

Bump Rules