release-automation

Automate software releases with versioning, changelog generation, Git tagging, and publishing.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/manastalukdar/claude-devstudio --skill release-automation-manastalukdar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-automation
Source: https://github.com/manastalukdar/claude-devstudio/tree/main/skills/release-automation
Command: npx skills add https://github.com/manastalukdar/claude-devstudio --skill release-automation-manastalukdar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the entire software release process, from version bumping and changelog generation to tagging and publishing, saving developers significant time and reducing manual errors.

Core Features & Use Cases

  • Automated Versioning: Supports semantic versioning (major, minor, patch) and explicit version setting.
  • Changelog Generation: Automatically creates or updates CHANGELOG.md based on conventional commits.
  • Publishing: Handles publishing to various package registries (npm, PyPI, Cargo, etc.) and creating platform releases (GitHub/GitLab).
  • Use Case: A developer can invoke this skill with a simple command like /release-automation minor to automatically update version numbers, generate a changelog, tag the release, and push it to the remote repository.

Quick Start

Run the release-automation skill to automatically determine the next version based on your commit history and create a patch release.

Frequently Asked Questions about release-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumping and changelog generation from conventional commits?

Automate version bumping and changelog generation by running a release pipeline that parses conventional commits to update semantic versioning and automatically create or update CHANGELOG.md.

What is the best way to publish a package and create a Git tag in one step?

The best way to publish a package and create a Git tag in one step is to use a release automation pipeline that handles Git tagging, version bumping, and registry publishing seamlessly.

Can I use release automation to publish packages to multiple registries like npm and PyPI?

Yes, you can use release automation to publish packages to multiple registries. It handles publishing across various platforms including npm, PyPI, Cargo, and others.

How does semantic versioning work with automated release pipelines?

Automated release pipelines apply semantic versioning by determining the next major, minor, or patch version based on your commit history, ensuring progressive and safe release steps.

Do I need to manually edit CHANGELOG.md before triggering an automated release?

No, you do not need to manually edit CHANGELOG.md. The release automation automatically generates or updates the changelog based on your conventional commit history.