changesets
Installation
SKILL.md
Treat a changeset as the release note for the complete PR, not as a log of work performed along the way. Finalize it after the current implementation scope and focused validation are complete.
Workflow
- Inspect the complete diff from the merge base, including changeset files already introduced by the PR, and identify directly affected published packages.
- Classify impact across source types, runtime behavior, entrypoints, required services, lifecycle, and persisted or wire data.
- Perform the breaking audit below.
- Record a reason no changeset is required, or update the PR's existing changeset. Create one only when the PR does not have one. When required, read authoring.md.
- Validate package names, frontmatter, bump policy, and a concise consumer-facing description.
Do not include unrelated worktree changes.