releasing-to-pypi

What problem does it solve?

This Skill prevents costly errors and failed releases to PyPI by enforcing a strict, atomic checklist for code linting, version bumping, tagging, and documentation updates before any code is committed or pushed.

Core Features & Use Cases

• Atomic Release Process: Ensures all release-critical steps are completed in a single, verifiable commit.
• Version Consistency: Guarantees that version numbers are updated across all relevant files (pyproject.toml, init.py, tests, CHANGELOG.md).
• CI/CD Safety: Prevents release failures by ensuring the tagged commit is production-ready, avoiding immutable PyPI filename conflicts.
• Use Case: Before pushing a new feature, use this Skill to run linters, update the version number in 10 files, verify the changelog, and create the Git tag and GitHub release in one go.

Quick Start

Follow the checklist in this skill to prepare and release your code to PyPI.