Prepare Release

VerifiedSafe

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

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

Recommended for

Our review

Automates the steps to prepare a new version release: version bump, CHANGELOG update, and package build.

Strengths

  • Prevents manual errors in release prep
  • Integrates CHANGELOG update with current date
  • Cleans and rebuilds distribution files

Limitations

  • Assumes a Python project with pyproject.toml
  • Does not push or deploy
  • Does not publish to PyPI
When to use it

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

When not to use it

For simple releases without a CHANGELOG or formal versioning scheme.

Security analysis

Safe
Quality score85/100

The skill uses local project-specific file cleanup (rm -rf dist/ build/ *.egg-info) and build commands (python -m build). No network exfiltration, no system-wide destructive operations, no obfuscation or disabling of safety mechanisms.

No concerns found

Examples

Prepare release 0.4.1
Prepare a release for version 0.4.1. Update version files, update CHANGELOG, build the package, and verify.
Bump version and rebuild
Run the release preparation for version 0.5.0: update version, move unreleased changelog entries under the new header, and rebuild the distribution.

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