Release Preparation

VerifiedSafe

Automates version bumping in pyproject.toml and __init__.py, CHANGELOG updates, and package building. Helps streamline pre-release tasks.

Sby Skills Guide Bot
DevelopmentIntermediate
906/2/2026
Claude Code
#release#versioning#changelog#build

Recommended for

Our review

Automates the steps to prepare a new release: updating version number, changelog, and building the package.

Strengths

  • Ensures consistency across version files (pyproject.toml, __init__.py)
  • Structures the CHANGELOG with properly dated sections
  • Cleans and rebuilds distribution files reliably

Limitations

  • Specifically designed for Python projects using pyproject.toml
  • Does not publish the release (preparation only)
  • Requires user to provide the version number
When to use it

When you need to prepare a new version of a Python package before publishing.

When not to use it

If you're looking for a complete publishing tool (use a CI/CD workflow instead).

Security analysis

Safe
Quality score85/100

The skill only runs standard Python build commands and a targeted rm for cleanup. No exfiltration, no disabling of safety, no obfuscation.

No concerns found

Examples

Prepare version 0.4.1
Prepare a release for version 0.4.1.
Update changelog and build
Run the release preparation steps: update version to 1.0.0, update changelog, and build the package.

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