Manage Changelog Skill
This skill enables the agent to manage project changelogs efficiently using Changie. It supports the full lifecycle from initialization to release.
When to Use
- •When you need to initialize a changelog for a new project.
- •When you want to record a change (feature, bug fix, etc.) after completing a task.
- •When preparing for a new release and batching unreleased changes.
Instructions
1. Initialization
If the project doesn't have changie set up, run the initialization script:
bash
.cursor/skills/manage-changelog/scripts/init-changie.sh
This will create .changie.yaml with standard workspace settings. For details on the configuration, see references/configuration.md.
2. Adding Changes
To add a new change fragment:
bash
changie new --kind <kind> --body "<description>"
- •Kinds: See references/configuration.md for a list of valid kinds.
- •Helper Script: Alternatively, use
.cursor/skills/manage-changelog/scripts/add-from-last-commit.shto create a fragment from the last commit message.
3. Batching a Release
When you are ready to create a new version:
bash
# Preview next version changie next auto # Batch unreleased changes into a version changie batch auto
For more details on versioning arguments and dry-run flags, see references/command-details.md.
4. Merging into CHANGELOG.md
To update the main CHANGELOG.md file:
bash
changie merge
References
- •Best Practices: Workflow tips and content standards.
- •Command Details: Detailed explanation of flags and utility subcommands.
- •Configuration Guide: Kinds, directory structure, and config details.
- •CLI Help Reference: Raw output from
changie --help.