release-manager

Automate changelog generation, version bumps, and GitHub releases.

3|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/grasberg/sofia --skill release-manager-grasberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/grasberg/sofia/tree/main/workspace/skills/release-manager
Command: npx skills add https://github.com/grasberg/sofia --skill release-manager-grasberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing software often bottlenecks on predictable communication and packaging. This Skill centralizes release orchestration to automate changelogs, version bumps, tags, and release artifacts, making each release clear to users and maintainers.

Core Features & Use Cases

  • Determine version bumps using a semantic versioning decision tree.
  • Generate changelogs with categorized entries, linked PRs, and reader-focused summaries.
  • Create migration guides for breaking changes and publish annotated Git tags.
  • Publish GitHub releases and notify stakeholders and downstream users.
  • Support common release workflows (trunk-based, git-flow, release train).

Quick Start

Initialize the release workflow for the current project release to generate a changelog, determine a version bump, tag the release, and publish a GitHub release.

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 and semantic versioning for GitHub releases?

Automate changelog generation and semantic versioning by applying a decision tree to your commits, bumping versions accordingly, and publishing categorized release notes directly to GitHub releases.

What is the best way to generate a migration guide for breaking changes in a software release?

Generate a migration guide for breaking changes by using built-in templates that document version transitions, ensuring downstream users and stakeholders receive clear, structured upgrade communications.

Does this release management approach support both trunk-based and git-flow workflows?

Yes, this release management approach supports common workflows including trunk-based, git-flow, and release train models, allowing you to orchestrate version bumps and tags across your preferred branching strategy.

How do I create annotated Git tags for a new software release?

Create annotated Git tags for a new release by initializing the release workflow, which automatically determines the semantic version bump and applies the tag to mark the specific project state.

Can I notify stakeholders automatically when publishing a GitHub release?

Yes, you can notify stakeholders automatically as part of the release publication steps, which orchestrate downstream user communications alongside tagging and publishing the GitHub release.

When should I use a semantic versioning decision tree for version bumps?

Use a semantic versioning decision tree for version bumps when your software project requires structured release communications, ensuring accurate version increments for features, patches, and breaking changes.