prep_release

Automates version bumps, changelog updates, builds, and PyPI deployment for Python packages.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/tatsuki-washimi/gwexpy --skill prep-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prep_release
Source: https://github.com/tatsuki-washimi/gwexpy/tree/main/.agent/skills/prep_release
Command: npx skills add https://github.com/tatsuki-washimi/gwexpy --skill prep-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill automates pre-release tasks to ensure a clean, consistent release process across versioning, changelog maintenance, and deployment.

Core Features & Use Cases

  • Version management: update versions in pyproject.toml and init.py.
  • Changelog upkeep: generate and organize CHANGELOG.md entries.
  • Build and publish: build distribution artifacts and prepare for PyPI or TestPyPI.

Quick Start

Invoke the release prep tool to guide the release workflow and optionally run in --build, --testpypi, or --production modes.

Frequently Asked Questions about prep_release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Python package versioning and changelog updates before a release?

Automating Python release preparation coordinates version bumps in pyproject.toml and __init__.py alongside CHANGELOG.md generation, ensuring consistent versioning and changelog upkeep across your software team's release workflow.

What is the best way to build Python distribution artifacts and publish to TestPyPI?

Building Python distribution artifacts and publishing to TestPyPI is orchestrated through release preparation modes like --build and --testpypi, which handle distribution creation and deployment verification steps before a production release.

How do I update pyproject.toml and __init__.py versions consistently for a PyPI release?

Updating pyproject.toml and __init__.py versions consistently is handled by release automation that applies synchronized version bumps across project files, preventing mismatched version numbers during Python package deployment.

Can I generate and organize CHANGELOG.md entries automatically as part of my Python build process?

Generating and organizing CHANGELOG.md entries automatically is supported during release preparation, applying structured changelog updates described in the repository references to maintain consistent release documentation.

Does this release preparation workflow support publishing directly to production PyPI?

Publishing directly to production PyPI is supported through the --production mode, which executes the build orchestration and deployment steps required for final distribution after version and changelog updates are verified.

What files need to be modified when preparing a Python package for release to PyPI?

Files modified when preparing a Python package release include pyproject.toml for project metadata, __init__.py for version strings, CHANGELOG.md for release notes, and the generated distribution artifacts for deployment.