repomatic-release

Automate pre-release checks, version bumping, changelog updates, and Git tagging for Python packages.

57|8|Updated Dec 9, 2021
One-click install
npx skills add https://github.com/kdeldycke/repomatic --skill repomatic-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repomatic-release
Source: https://github.com/kdeldycke/repomatic/tree/main/.claude/skills/repomatic-release
Command: npx skills add https://github.com/kdeldycke/repomatic --skill repomatic-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and repetitive tasks involved in preparing, validating, and executing Python package releases, reducing manual effort and potential errors.

Core Features & Use Cases

  • Release Pre-checks: Validates repository state, changelog consistency, and version accuracy before release.
  • Release Preparation: Automates version bumping, changelog updates, and commit generation for release.
  • Post-Release Validation: Assists in verifying that all release artifacts and steps are completed.
  • Use Case: A developer can use this skill to ensure their package is ready for PyPI upload, automatically generating the necessary commits and tags, and then confirming all release steps were followed.

Quick Start

Use the repomatic-release skill to prepare for a new package release.

Frequently Asked Questions about repomatic-release

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

FAQPage Schema
How do I automate Python package releases to PyPI?

Automate Python package releases by running pre-release checks, bumping versions, updating changelogs, and generating Git tags to ensure consistency across pyproject.toml and PyPI uploads.

How do I keep pyproject.toml versions consistent with Git tags and changelogs?

Keep pyproject.toml versions consistent by validating repository state and synchronizing version numbers across changelog.md and Git tags during release preparation and post-release validation.

Can I use this automation for downstream repositories instead of just canonical Python packages?

Yes, you can use this release automation for both canonical and downstream repositories, ensuring version bumping, changelog updates, and Git tagging remain consistent across different repository structures.

What pre-release checks are needed before uploading a Python package to PyPI?

Pre-release checks for Python packages validate repository state, verify changelog consistency, and confirm version accuracy in pyproject.toml to prevent errors before generating release commits and tags.

What is the best way to automate version bumping and changelog updates for Python packages?

The best way to automate version bumping and changelog updates is using a release workflow that modifies pyproject.toml and changelog.md, then automatically generates the necessary Git commits and tags.

Why do my Python package releases fail due to inconsistent changelog and version states?

Python package releases fail when version numbers in pyproject.toml do not match Git tags or changelog entries; automating pre-release validation checks prevents these inconsistencies.