Menu
Create a changeset file for versioning and changelog generation. Use when the user asks to add a changeset, bump version, or prepare a release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | add-changeset |
| description | Create a changeset file for versioning and changelog generation. Use when the user asks to add a changeset, bump version, or prepare a release. |
First Todo list item: Find the code in this PR to get context.
patch, minor, or major, use AskUserQuestion to prompt them:
Only prompt if they do not provide it
Create a changeset file in .changeset/ directory with a descriptive name based on the feature or change (e.g., add-dark-mode.md, fix-login-bug.md, rename-config-fields.md)
Add a todo at the end to verify the changeset with bun run changeset status
File: .changeset/add-export-feature.md
---
"patchy-cli": patch
---
Add CSV export functionality for usage metrics
---
"package-name": patch|minor|major
---
Description of the change (used in CHANGELOG)
Name changeset files descriptively based on the change:
add-dark-mode.md (new feature)fix-auth-timeout.md (bug fix)rename-config-fields.md (refactor)breaking-api-v2.md (breaking change)Avoid random/generated filenames.