manage-changelog
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Manage changelogs using Changie. Provides tools to initialize, add change fragments, batch releases, and merge version notes. Requires 'changie' to be installed.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When you need to initialize a changelog for a new project.
- Distinctive: line 13
When you want to record a change (feature, bug fix, etc.) after completing a task.
- Distinctive: line 14
When preparing for a new release and batching unreleased changes.
- Very specific: line 20
If the project doesn't have changie set up, run the initialization script:
- Distinctive: line 41
When you are ready to create a new version:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
.claude/skills/manage-changelog/scripts/init-changie.shThis will create .changie.yaml with standard workspace settings.
2. Adding Changes
To add a new change fragment:
changie new --kind <kind> --body "<description>"- Kinds: Typically
feat,fix,docs,refactor,test,chore. - Helper Script: Alternatively, use
.claude/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:
# Preview next version
changie next auto
# Batch unreleased changes into a version
changie batch auto4. Merging into CHANGELOG.md
To update the main CHANGELOG.md file:
changie mergeReferences
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

