release-planning

Automate software release planning with semantic versioning and changelog generation.

105|8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/686f6c61/alfred-dev --skill release-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-planning
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/devops/release-planning
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill release-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and often error-prone process of planning and executing software releases, ensuring consistency, clear communication, and adherence to best practices.

Core Features & Use Cases

  • Change Inventory: Automatically lists and classifies commits since the last release.
  • Semantic Versioning: Determines the correct version bump (MAJOR.MINOR.PATCH) based on changes.
  • Changelog Generation: Creates or updates the CHANGELOG.md file following the Keep a Changelog format.
  • Release Notes Drafting: Compiles detailed release notes for platforms like GitHub or GitLab.
  • Publishing: Guides through updating project version files, creating Git tags, and publishing releases.
  • Use Case: Before deploying version 2.0 of your application, use this Skill to ensure all new features are documented, breaking changes are clearly communicated, and the release is tagged correctly.

Quick Start

Use the release-planning skill to prepare the next release for the project.

Frequently Asked Questions about release-planning

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

FAQPage Schema
How do I automate semantic versioning and changelog generation for my git repository?

You can automate semantic versioning by inventorying git commits since the last release to determine the correct version bump and generating a changelog following the Keep a Changelog format.

What's the best way to draft release notes for breaking changes before a major version deployment?

Drafting release notes for breaking changes requires classifying commits to identify the major version bump and compiling detailed notes for platforms like GitHub or GitLab to clearly communicate impacts to users.

Can I use this release planning process to update project version files and create Git tags?

Yes, the release planning process guides you through updating project version files, creating Git tags, and publishing the final release notes to ensure the repository state matches the designated semantic version.

Does this release workflow support DevOps engineers and technical writers simultaneously?

Yes, the release workflow supports DevOps engineers by automating end-to-end release execution and technical writers by drafting clear release notes to streamline their respective release planning tasks.

When do I need to manually intervene in an automated software release workflow?

Manual intervention in an automated software release workflow is needed when verifying the generated change inventory, reviewing drafted release notes for accuracy, and approving the final Git tag and publishing steps before deployment.

How does change inventory classification determine the correct semver version bump?

Change inventory classification determines the semver version bump by listing and categorizing commits since the last release, identifying breaking changes for MAJOR, new features for MINOR, and patches for PATCH updates.