- Home
- Skills
- Technical Documentation
- make changelog
make changelog
Automate Keep a Changelog maintenance, SemVer calculation, and version bumping within your repository.
Free
Works with the AI Agents you already use
make changelog
Example session with this skill installed
I've finished the authentication fixes and added the new login endpoint. Update the changelog and bump the version to 1.1.0.
- Read your context and instructions
- Compiled the make changelog
I have updated the changelog with the authentication changes and bumped the project version to 1.1.0.
Changelog Update
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
## [1.1.0] - 2024-05-22
### Added
- New login endpoint for handling OAuth2 flows.
### Fixed
- Authentication token validation logic to prevent session hijacking.
Next steps
- Review the generated notes in
CHANGELOG.mdto ensure the descriptions match your internal terminology. - Verify that
package.jsonhas been updated from1.0.1to1.1.0. - Commit the changes and tag the release as
v1.1.0.
Connects securely to your tools. The creator never sees your data.
About this skill
Maintaining a changelog by hand leads to missed entries, inconsistent formatting, and versioning errors during release. This skill automates the lifecycle of your CHANGELOG.md, ensuring every notable change is captured and formatted according to the Keep a Changelog 1.1.0 standard.
What it does
- Standardized formatting applies the Keep a Changelog spec with sections for Added, Changed, Deprecated, Removed, Fixed, and Security.
- Smart diff analysis scans your task's changes to generate concise, user-focused bullets while ignoring noise like lockfiles or tool configs.
- Monorepo support detects workspace structures to manage either a single root changelog or individual logs per package.
- Automated versioning calculates the next SemVer bump based on the types of changes recorded in the unreleased section.
- Synchronized updates writes new version numbers directly into your project files, such as package.json, when you trigger a release.
How it works
- Initialize the environment with
/make-changelog initto create the standard file structure and standing blocks. - Update the unreleased section by requesting a record of recent changes or using
/make-changelog update. - Bump the version by requesting a release, which moves notes to a dated heading and updates the product version field.
Frameworks & tools
This skill is language-agnostic and works with any project using SemVer or custom versioning schemes. It recognizes monorepo patterns and integrates with standard metadata files like package.json or workspace configuration files.
Why this beats prompting it yourself
Generic prompts often hallucinate version numbers or fail to distinguish between internal refactors and user-facing changes. This skill enforces strict invariants, such as YYYY-MM-DD dating and specific section ordering, while maintaining link footers and tag prefixes exactly as your repo requires.
Use cases
- Documenting new features and fixes before a pull request is merged.
- Cutting a new release version across multiple packages in a monorepo.
- Retroactively catching up a changelog by scanning recent commit history.
- Transitioning a legacy project to the Keep a Changelog standard.
Known limitations
Does not scan the file tree for monorepo signals unless workspace members are explicitly listed. Requires manual confirmation before rewriting files that do not appear to be changelogs.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires explicit monorepo signals to manage package-specific logs. Won't bump versions unless specifically requested. Asks for confirmation before rewriting non-standard files.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
1 use
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account