Stele Release FAQs

Question 1

When should I use this Claude Code Skill?

Accepted Answer

You should invoke this skill whenever you are ready to ship new changes. Simply ask Claude to 'prepare a release' or 'bump the version,' and the skill will guide you through the analysis, testing, and tagging process.

Question 2

How does it determine the next version number?

Accepted Answer

The skill utilizes a specialized Python script to scan your Git history for conventional commit patterns. It detects breaking changes for major versions, 'feat' for minor versions, and 'fix' for patch versions, ensuring strict adherence to Semantic Versioning.

Question 3

What happens if a release fails after the tag is pushed?

Accepted Answer

The skill includes detailed rollback procedures. It provides specific commands to delete both local and remote tags, allowing you to fix the underlying issue and restart the release process without polluting your version history.

Question 4

What does the Stele Release skill do?

Accepted Answer

This skill automates the entire release lifecycle for the Stele CLI. It analyzes conventional commits to suggest version bumps, runs pre-release validations (like Go tests), handles Git tagging, and coordinates with GitHub Actions for binary distribution.

Question 5

Does it support pre-release versions like betas?

Accepted Answer

Yes. The skill can handle stable releases (v1.0.0) as well as pre-release versions (v1.0.0-beta.1). It integrates with GoReleaser to automatically flag these as pre-releases on GitHub.

Stele Release

Stele Release

Key Features

Use Cases

Key Features

Use Cases