- Home
- Skills
- DevOps & Cloud
- changelog automation
changelog automation
Automate semantic versioning and Keep a Changelog generation using Conventional Commits.
$1.49
Works with the AI Agents you already use
changelog automation
Example session with this skill installed
Set up standard-version for a Node.js project to automate patch releases and update CHANGELOG.md.
- Read your context and instructions
- Compiled the changelog automation
I have configured standard-version for your project. This setup includes the necessary configuration file and package.json scripts to handle automated versioning and changelog updates following the Keep a Changelog format.
Implementation Details
// .versionrc.js
module.exports = {
types: [
{ type: "feat", section: "Features" },
{ type: "fix", section: "Bug Fixes" },
{ type: "perf", section: "Performance Improvements" },
{ type: "revert", section: "Reverts" },
{ type: "docs", section: "Documentation", hidden: true },
{ type: "style", section: "Styles", hidden: true },
{ type: "chore", section: "Miscellaneous", hidden: true },
{ type: "refactor", section: "Code Refactoring", hidden: true },
{ type: "test", section: "Tests", hidden: true },
{ type: "build", section: "Build System", hidden: true },
{ type: "ci", section: "CI/CD", hidden: true },
],
releaseCommitMessageFormat: "chore(release): {{currentTag}}",
scripts: {
prechangelog: 'echo "Updating CHANGELOG.md..."',
postchangelog: 'echo "Changelog updated successfully."'
}
};
Update your package.json with these scripts:
{
"scripts": {
"release": "standard-version",
"release:patch": "standard-version --release-as patch",
"release:minor": "standard-version --release-as minor",
"release:major": "standard-version --release-as major",
"release:dry": "standard-version --dry-run"
},
"devDependencies": {
"standard-version": "^9.5.0"
}
}
Next steps
- Run
npm install -D standard-versionto add the dependency. - Execute
npm run release:dryto preview the changes without committing. - Use
npm run release:patchfor your first automated release.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual changelog maintenance is error prone and inconsistent. This skill implements standardized release workflows to automate versioning and documentation from your git history.
What it does
- Automates changelog generation using Conventional Commits to build industry standard
CHANGELOG.mdfiles. - Enforces commit standards via
commitlintandhuskyto ensure git history is machine readable. - Manages semantic versioning by calculating major, minor, and patch increments based on commit types.
- Configures release pipelines for GitHub Actions, Node.js, Python, and Rust environments.
- Generates release notes including contributor lists, breaking change alerts, and comparison links.
How it works
- Initialize conventions by setting up
commitlintand git hooks to validate developer input. - Select implementation from supported tools like
semantic-release,standard-version,git-cliff, orcommitizen. - Configure automation using provided
.versionrc.js,release.config.js, orcliff.tomlpatterns. - Trigger releases through CLI commands or automated GitHub Actions workflows.
Frameworks & tools
Supports Node.js (npm), Python (pip, pyproject.toml), and Rust (git-cliff). Integrates with GitHub Actions, GitLab, and Husky for CI/CD automation.
Why this beats prompting it yourself
Building a reliable release pipeline requires deep knowledge of Semantic Versioning and tool-specific configuration. This skill provides production-ready config files and regex-based parsers that avoid the common pitfalls of manual version bumping.
Use cases
- Migrating a legacy repo to the Keep a Changelog standard.
- Setting up zero-touch deployments where CI handles the versioning and tagging.
- Enforcing strict commit message formats across a large engineering team.
- Creating internal release summaries that highlight business value over raw diffs.
Known limitations
Requires a clean git history following Conventional Commits to generate meaningful output. Full automation requires write permissions to the repository's contents and tags.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Requires git history to follow Conventional Commits. Full automation requires repo write permissions. Non-standard commit types may be ignored by default parsers.
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
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
- Software
- husky
Node.jscommitlintsemantic-releasestandard-version