release-manager

Automate release management by parsing conventional commits and generating changelogs.

Updated May 24, 2026
One-click install
npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill release-manager-haj1t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/haJ1t/senior-dev-squad-skills/tree/main/plugins/senior-dev-squad/skills/release-manager
Command: npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill release-manager-haj1t

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, CI/CD tools, package managers, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The release-manager Skill eliminates manual errors in software release processes, ensuring every release is documented, tagged, and validated automatically.

Core Features & Use Cases

  • Automated Release Management: Automates tagging, changelog generation, and package publishing for software projects.
  • Semantic Versioning: Parses conventional commit messages to calculate semantic versions accurately.
  • Git Tagging and Branch Management: Manages git tags and creates release branches for consistent and traceable releases.
  • Package Publishing: Publishes packages to target repositories, such as npm, PyPI, or GitHub Releases.
  • Use Case: This Skill is ideal for teams under time pressure, working with multi-package repositories, or releasing during off-hours to minimize human error.

Quick Start

Use the release-manager skill to automatically tag, generate a changelog, and publish a new release for your project.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I automate changelog generation from conventional commit messages?

Automated changelog generation parses conventional commit messages to extract features, fixes, and breaking changes, creating structured release notes while managing semantic versioning and git tags automatically.

What's the best way to manage semantic versioning and git tagging for releases?

Managing semantic versioning and git tagging is automated by parsing conventional commit messages to calculate version bumps accurately, creating release branches, and validating builds before publishing packages.

Can I use this release management process for multi-package repositories?

Yes, this release management process is ideal for teams working with multi-package repositories, as it automates tagging, changelog generation, and package publishing to minimize human error during releases.

Do I need git and CI/CD tools to automate package publishing?

Yes, automating package publishing requires git, CI/CD tools, and package managers for execution, ensuring every release is documented, tagged, and validated without manual intervention.

How does automated semantic versioning calculate version bumps from commits?

Automated semantic versioning calculates version bumps by parsing conventional commit messages, detecting breaking changes for major bumps, new features for minor bumps, and fixes for patch bumps.

Why should I automate release management instead of tagging manually?

Automating release management eliminates manual errors in software release processes, ensuring every release is consistently documented, tagged, and validated automatically across your target package repositories.