Release Preparation

VerifiedSafe

Automates release preparation steps including version bumping, CHANGELOG management, package building, and verification.

Sby Skills Guide Bot
DevelopmentIntermediate
206/2/2026
Claude Code
#release#versioning#changelog#package-build#python

Recommended for

Our review

This skill automates the steps required to prepare a new version release, including version update, changelog update, and package build.

Strengths

  • Automates repetitive release tasks
  • Ensures consistency across version files
  • Integrates package verification with twine

Limitations

  • Requires project to use pyproject.toml and CHANGELOG.md
  • Assumes Python packages only
  • Does not handle publishing to PyPI
When to use it

When you need to prepare a new version of a Python package in a structured and repeatable way.

When not to use it

When you are using an automated release tool (like bumpversion, semantic-release) or if your project does not follow a standard versioning pattern.

Security analysis

Safe
Quality score85/100

The skill performs routine local file operations (rm, python build, twine check) within the project directory, with no destructive or exfiltrating behavior, and no obfuscation or disabling of safety features.

No concerns found

Examples

Prepare release v0.4.1
Prepare a release for version 0.4.1 including version update, changelog update, and build.
New release for current project
Please prepare a release for my Python package. The new version is 0.5.0.

name: prep_release description: バージョン更新、CHANGELOG整備、パッケージビルドなど、リリース前の準備を行う

Prepare Release

This skill automates the steps required to prepare a new version release.

Instructions

  1. Update Version:

    • Ask the user for the new version number (e.g. 0.4.1).
    • Update version in pyproject.toml.
    • Update __version__ variable in gwexpy/__init__.py if it exists.
  2. Update Changelog:

    • Read CHANGELOG.md.
    • Create a new header for the new version with the current date.
    • Move "Unreleased" changes under this new header.
  3. Build Package:

    • Clean old distribution files: rm -rf dist/ build/ *.egg-info.
    • Run build command: python -m build.
    • Check if correct .tar.gz and .whl files are created in dist/.
  4. Verify:

    • (Optional) Run twine check dist/* to verify metadata validation if twine is available.
Related skills