Create a new release version. Use when asked to create a release, prepare a release, bump version, or update the changelog.
This skill guides the process of creating a new release for the notes application.
When the user asks to create a release, follow these steps:
Use the AskUserQuestion tool to ask the user what type of release this is:
Options:
Read package.json to get the current version. Parse the semantic version (MAJOR.MINOR.PATCH) and increment the appropriate number:
Use AskUserQuestion or ask the user directly what changes should be documented in this release. The changelog follows this format:
## [VERSION] - YYYY-MM-DD
### New Features
- Feature descriptions here
### Improvements
- Improvement descriptions here
### Bug Fixes
- Bug fix descriptions here
### Database Changes
- Any schema changes here (remind to run migrations)
Only include sections that have content.
Update package.json: Change the version field to the new version number
Update CHANGELOG.md: Add the new version section at the top (after the header), above all existing versions
Run the following command to check if there are any pending schema changes:
bun run db:generate
If new migrations are generated:
bun run db:push (dev) or bun run db:migrate (prod) after deploymentIf no changes are detected, confirm that migrations are up to date.
Provide a summary of what was done:
## [0.2.0] - 2026-01-15
### New Features
**Feature Name**
- Description of the feature
- Additional details
### Improvements
**Area of Improvement**
- What was improved
### Database Changes
- Added `column_name` to `table_name` table
> **Note:** Run `bun run db:push` to apply the schema migration.