release-manager

Automate changelog generation, version bumping, and rollback procedures from Git history.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/saschadudkin-sketch/rezidence4 --skill release-manager-saschadudkin-sketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/saschadudkin-sketch/rezidence4/tree/main/.agents/skills/release-manager
Command: npx skills add https://github.com/saschadudkin-sketch/rezidence4 --skill release-manager-saschadudkin-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires changelog_generator, version_bumper, release_planner, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the software release process, eliminating manual steps, automating repetitive tasks, and enforcing best practices for versioning, changelogs, and deployment.

Core Features & Use Cases

  • Automated Changelog Generation: Generates structured changelogs from git history using conventional commits.
  • Semantic Version Bumping: Determines the correct version bump based on commit analysis and breaking changes.
  • Release Readiness Assessment: Assesses release readiness with comprehensive checklists and validation.
  • Release Planning & Coordination: Generates release coordination plans with stakeholder communication templates.
  • Rollback Planning: Automates rollback procedures with automated recovery procedures.
  • Hotfix Management: Manages hotfixes for emergency releases.
  • Feature Flag Integration: Enables safe, progressive rollouts with feature flags.

Quick Start

Use the release-manager skill to generate a changelog for your latest release from the 'master' branch.

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 commits for a new release?

Automated changelog generation parses your git history using conventional commits to produce structured release notes. This streamlines software release management by eliminating manual documentation steps for your master branch.

How does semantic version bumping work when analyzing git history for breaking changes?

Semantic version bumping analyzes your git commit history to determine the correct version increment. It automatically identifies breaking changes to trigger major version bumps, while standard commits trigger minor or patch updates.

Do I need Python and Git to run release planning and rollback procedures?

Yes, you need Python 3.7+ and Git installed to execute release planning and rollback procedures. These dependencies are required to parse git history and run the automation scripts for version bumping and coordination.

What is the best way to manage hotfixes and coordinate emergency software releases?

Hotfix management automates emergency software releases by generating specific rollback procedures and stakeholder communication templates. This ensures rapid, coordinated deployment while maintaining release readiness assessment standards.

Can I use feature flag integration for progressive rollouts during release coordination?

Yes, feature flag integration enables safe, progressive rollouts during release coordination. This allows you to decouple deployment from release, managing feature visibility safely without disrupting the automated semantic versioning workflow.

Why does release readiness assessment fail without conventional commit formatting?

Release readiness assessment relies on conventional commit formatting to validate git history and generate accurate changelogs. Without standardized commit messages, automated version bumping and structured release notes cannot be parsed correctly.