skills.rest
mdnaimul22
mdnaimul22COMMUNITY
Explore all skills by this author →
GitHub

release-manager

Generate changelogs, semantic versions, and release plans from conventional commits.

2|Updated Apr 15, 2026
Search Tags:#conventional commits#semantic versioning#release planning#changelog generation#devops readiness#rollback runbook
One-click install
npx skills add https://github.com/mdnaimul22/human-skills --skill release-manager-mdnaimul22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/mdnaimul22/human-skills/tree/main/skills/release-manager
Command: npx skills add https://github.com/mdnaimul22/human-skills --skill release-manager-mdnaimul22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Release Manager helps teams avoid risky, error-prone deployments by turning conventional-commit history into dependable changelogs, by calculating correct semantic version bumps, and by producing structured release readiness and coordination plans.

Core Features & Use Cases

  • Changelog generation from conventional commits: Converts git history into organized changelog sections, highlights breaking changes, and extracts issue/PR references.
  • Semantic version bump determination: Recommends major/minor/patch (and pre-releases) by analyzing commit types and breaking-change indicators.
  • Release readiness and coordination planning: Assesses readiness using quality gates and approvals, creates checklists, communication plans, rollback/runbook guidance, and risk-focused recommendations.
  • Use case: Preparing a Winter 2024 release by generating a changelog draft, computing the next version from commit history, then producing a go/no-go report with rollout, stakeholder updates, and rollback procedures.

Quick Start

Ask the assistant: "Plan my next release by generating a changelog, recommending the version bump from conventional commits, and producing a release readiness report using assets/sample_release_plan.json."

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I generate a changelog from conventional commits automatically?▼

Changelog generation from conventional commits organizes git history into structured sections, highlights breaking changes, and extracts issue/PR references. You provide conventional commit history and a structured release-plan JSON to produce machine-readable Markdown or text outputs.

How do I determine the correct semantic version bump from commit history?▼

Semantic version bump determination analyzes conventional commit types and breaking-change indicators to recommend major, minor, or patch increments. It correctly handles version precedence and pre-release labeling based on the parsed commit history.

What is a release readiness report and how is it calculated?▼

A release readiness report assesses deployment safety using quality gates and approvals to produce a go/no-go score. It identifies blocking issues, generates rollout checklists, stakeholder communication plans, and rollback runbooks.

Can I use this for hotfix release planning and rollback coordination?▼

Hotfix release planning is supported through rollback runbook generation and risk-focused recommendations. The system produces structured coordination plans that include rollback procedures and stakeholder updates for scheduled deployments and hotfixes.

Do I need a structured JSON input for release planning or can I just use git history?▼

You need both conventional commit history and a structured release-plan JSON input for release planning. The JSON input provides quality gates and approval parameters, while the commit history supplies the changelog and semantic version data.

What are the limitations of using semantic versioning for pre-release handling?▼

Semantic versioning pre-release handling correctly applies version precedence rules but requires strictly formatted conventional commits to detect breaking changes accurately. Malformed commit messages will prevent correct version bump recommendations and readiness scoring.

Related Skills

Explore More Software Engineering Skills→
Sir-chawakornSir-chawakorn
9

release-notes

Generate changelogs from git history using Conventional Commit standards.

Community
Advanced
erphqerphq
2

deployment-golive

Plan environments, cutover runbooks, rollback procedures, and go/no-go decisions for production deployment.

Official
Advanced
OpenLaborOpenLabor
4

Deployment

Coordinate and automate application deployments across environments with rollout strategies.

Official
Intermediate
Iron-HamIron-Ham
29

release-preview

Preview version bumps, changelog updates, and release notes without modifying the repository.

Community
Advanced