release

Release Skill

Automates the release management workflow for any project, following semantic versioning and Keep a Changelog conventions. Works with Python, Node.js, and other project types through automatic version file detection.

Usage

/release minor              # Create minor version release (1.1.0 -> 1.2.0)
/release patch              # Create patch version release (1.1.0 -> 1.1.1)
/release major              # Create major version release (1.0.0 -> 2.0.0)
/release hotfix v1.1.0      # Create hotfix from v1.1.0 tag
/release test               # Create TestPyPI test release

Authorization Notice

IMPORTANT: This repository uses a fork-based workflow.

• Maintainers (@itdove): Can use this skill to create and push releases
• Contributors: Should NOT create or push production tags
  • Fork the repository instead (see CONTRIBUTING.md)
  • Submit pull requests with changes
  • Update CHANGELOG.md in your PR
  • Maintainers will handle releases

If you are a contributor (not @itdove):

• ✅ You can use /release test for local testing
• ✅ You can use the skill to understand the process
• ❌ DO NOT push production tags (v1.2.0, etc.)
• ✅ Let maintainers create releases from your PRs

Skill Invocation

When invoked with arguments (e.g., /release minor), this skill guides you through:

1. Safety Checks: Verify prerequisites before starting
2. Release Readiness CI: Trigger automated readiness workflow and wait for results
3. Version Management: Update version in both required files
4. CHANGELOG Management: Update CHANGELOG.md with proper format
5. Git Operations: Create branches, commits, and tags
6. Post-Release Guidance: Provide checklist for manual steps (maintainers only)

Release Types

Regular Release (/release major|minor|patch)

Purpose: Create a new production release from main branch

Prerequisites:

• All tests pass on main
• CHANGELOG.md has Unreleased section with changes
• Main branch is up-to-date