Release cryptobot-python package

VerifiedCaution

Automates the release process for the cryptobot-python package: validates version, updates files, creates git tag and GitHub release. Useful when you need to cut a new version, update HISTORY.md, or publish a release.

Sby Skills Guide Bot
DevOpsIntermediate
606/2/2026
Claude CodeCursorWindsurf
#release#version-bump#git-tag#github-release#changelog

Recommended for

Our review

Automates the preparation and publication of a new release for the cryptobot-python package.

Strengths

  • Reduces manual errors by automating version file updates
  • Runs tests before release to ensure quality
  • Creates a git tag and GitHub release automatically

Limitations

  • Specific to the cryptobot-python project structure (pyproject.toml, HISTORY.md)
  • Requires gh (GitHub CLI) to be installed and configured
  • Assumes make test is available and passes
When to use it

When you need to publish a new version of the cryptobot-python package, e.g., after accumulating changes.

When not to use it

For projects not using pyproject.toml or a HISTORY.md file, or if you prefer a manual release process.

Security analysis

Caution
Quality score85/100

The skill uses powerful tools like `make` and `gh` for release management. No destructive or exfiltration commands, but `make test` could run arbitrary code without user verification.

Findings
  • The skill instructs to run `make test` which executes potentially arbitrary commands from a Makefile. While likely legitimate for the project, it introduces execution risk if the Makefile is compromised.

Examples

Cut release 0.4.2
Cut a release for cryptobot-python version 0.4.2
New version 1.0.0
Prepare and publish a new release with version 1.0.0 for cryptobot-python
Release with notes
Create a release for cryptobot-python version 0.5.0, I will provide the release notes after you start.

name: release description: Prepare and publish a new cryptobot-python release. Use when the user asks to cut a release, bump the package version, update HISTORY.md, create a git tag, or create a GitHub release.

Release Skill

Create a new release for the cryptobot-python package.

Usage

/release <version>

Where <version> is the new semantic version (e.g., 0.4.2, 0.5.0, 1.0.0).

Instructions

When the user invokes this skill with a version number, perform the following steps:

  1. Validate the version: Ensure the version follows semantic versioning (X.Y.Z format).

  2. Update version files:

    • Update version in pyproject.toml
    • Update __version__ in cryptobot/__init__.py
  3. Ask for release notes: Ask the user what changes should be included in the release notes.

  4. Update HISTORY.md: Add a new entry at the top of the History section with:

    • Version number and today's date
    • The release notes provided by the user
  5. Run tests: Execute make test to ensure all tests pass before proceeding.

  6. Create commit: Create a commit with message chore(release): prepare v<version> release

  7. Create tag: Create an annotated git tag v<version> pointing to the release commit.

  8. Create GitHub release: Use gh release create to create a GitHub release with:

    • Tag: v<version>
    • Title: v<version>
    • Release notes from the HISTORY.md entry
  9. Report completion: Provide the user with:

    • Summary of files changed
    • Link to the GitHub release
Related skills