stele-release

Automate semantic version bumping and release preparation for the stele CLI project.

2|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/haleyrc/stele --skill stele-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stele-release
Source: https://github.com/haleyrc/stele/tree/main/.claude/skills/stele-release
Command: npx skills add https://github.com/haleyrc/stele --skill stele-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manual software release processes are prone to errors, time-consuming, and complex, especially when adhering to semantic versioning and generating changelogs. This Skill automates the entire workflow, from version analysis to tag creation and GitHub release monitoring, ensuring consistent and reliable deployments.

Core Features & Use Cases

  • Semantic Versioning: Automatically analyzes conventional commits to suggest the appropriate major, minor, or patch version bump.
  • Release Workflow Automation: Guides through pre-release checks, creates annotated Git tags, and triggers GitHub Actions for binary builds and changelog generation.
  • Use Case: When you've completed a set of features or fixes for your CLI tool, use this Skill to publish a new version effortlessly, ensuring a consistent, error-free release without manual Git commands or version calculations.

Quick Start

Navigate to your project root

cd /Users/ryan/dev/haleyrc/stele

Analyze commits and suggest the next version

python3 .claude/skills/stele-release/scripts/analyze_version.py

Frequently Asked Questions about stele-release

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

FAQPage Schema
How do I automate semantic versioning and releases for my CLI project?

Semantic versioning automation analyzes your conventional commits to determine whether to bump major, minor, or patch versions based on BREAKING CHANGE, feat:, and fix: prefixes, then guides you through tag creation and GitHub Actions workflows for consistent releases.

How do I analyze git commits to determine the next version bump?

Commit analysis parses your repository history for conventional commit patterns, evaluates breaking changes and feature additions, and suggests the appropriate semantic version increment before you create a release tag.

Can I automate git tag creation and GitHub release workflows?

Yes, the release automation creates annotated git tags, validates repository state (branch sync, tests), pushes tags to origin, and triggers GitHub Actions workflows to build binaries and generate changelogs automatically.

What checks does the release workflow run before creating a tag?

Pre-release validation ensures your repository branch is in sync, all tests pass, CI checks succeed, and the working directory is clean before proceeding with tag creation and release publication.

How do I monitor GitHub Actions after pushing a release tag?

After tag creation and push, the workflow provides monitoring and post-release verification steps to track binary builds and changelog generation, ensuring successful deployment before considering the release complete.