release

Automate Python release workflows by bumping versions, tagging commits, and creating GitHub Releases.

29|6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/acartag7/edictum --skill release-acartag7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/acartag7/edictum/tree/main/.claude/skills/release
Command: npx skills add https://github.com/acartag7/edictum --skill release-acartag7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the end-to-end release workflow to ensure consistent versioning, tagging, and publication across platforms.

Core Features & Use Cases

  • Version bumping and commit tagging for Python projects.
  • GitHub Release creation and PyPI publish verification integrated into a single workflow.
  • Use Case: When preparing a new release of a Python package, run the release skill to automatically bump the version, push commits, create a GitHub release, and verify PyPI deployment.

Quick Start

Provide the target version (e.g., /release 1.2.3) to perform an automatic bump, tag, push, release, and PyPI verification.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Python package version bumping and GitHub releases?

Automate Python package version bumping by updating pyproject.toml, tagging commits, and using the gh CLI to create GitHub releases. This enforces a consistent release sequence and pushes changes directly to the main branch.

Can I verify PyPI publishing when creating a GitHub release?

Yes, PyPI publishing verification is integrated into the GitHub release workflow. After pushing commits and creating the release, the process verifies PyPI deployment for the new package version.

How does CI/CD release automation work for Python projects?

CI/CD release automation for Python projects works by applying the release skill in local or pipeline environments to bump versions, push to the main branch, and create automated GitHub releases.

What is the best way to enforce a release sequence for Python packages?

The best way to enforce a release sequence is to use an automated workflow that updates pyproject.toml, commits and pushes changes, creates a GitHub release, and verifies PyPI deployment without manual intervention.

Do I need GitHub CLI to automate end-to-end releases?

Yes, GitHub CLI (gh) is required to create GitHub releases. The automated workflow relies on gh to finalize the release sequence after updating pyproject.toml and pushing commits.

Why does my automated release workflow fail to push tags to the main branch?

Automated release workflows fail to push tags when the release sequence is not properly enforced or pyproject.toml updates are incomplete, preventing successful commit tagging and GitHub release creation.