release

Name: release
Availability: InStock
Author: DonTizi

Automate Python project releases with version bumps, changelog updates, and Git tags.

2|Updated Jan 29, 2026

Search Tags:#automation #git #changelog #release #pypi #tagging #pyproject

Ready to run

npx skills add https://github.com/DonTizi/CodeGeass --skill release-dontizi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/DonTizi/CodeGeass/tree/main/.claude/skills/release
Command: npx skills add https://github.com/DonTizi/CodeGeass --skill release-dontizi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the release workflow for CodeGeass, updating version information, maintaining CHANGELOG, creating commits and Git tags, and publishing to PyPI to reduce manual release toil.

Core Features & Use Cases

Automated version bump: Update pyproject.toml with the new version.
Changelog maintenance: Add release notes under the new version in CHANGELOG.md.
Git operations: Commit changes, push to main, create and push tags.
PyPI publishing: Optional publishing to PyPI after the release.
Use Case: A maintainer releases a new CodeGeass version by running this skill to ensure a reproducible and auditable release process.

Quick Start

Run the release workflow with a new version tag, e.g. v$ARGUMENTS: codegeass release v$ARGUMENTS

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 publishing to PyPI with git tagging and changelog updates?▼

You can automate Python package publishing by updating version metadata in pyproject.toml, adding changelog entries to CHANGELOG.md, creating git commits and tags, and verifying CI actions before deploying to PyPI.

What is the best way to update pyproject.toml version and CHANGELOG.md for a new release?▼

The best way to update pyproject.toml and CHANGELOG.md for a new release is to apply an automated workflow that modifies version metadata, appends release notes under the new version, commits the changes, and pushes them to the main branch.

Can I publish to PyPI automatically after creating a git tag?▼

Yes, you can publish to PyPI after creating and pushing a git tag. The workflow supports optional PyPI publishing as the final step once the version bump, changelog update, and git tagging are complete.

Does this release workflow verify CI actions before publishing to PyPI?▼

Yes, the release workflow verifies CI actions before publishing to PyPI. It checks the CI status as a prerequisite to ensure that the continuous integration pipeline passes before the final package deployment occurs.

What are the limitations of automating git tagging and version bumps for Python projects?▼

A limitation of automating git tagging and version bumps is the strict dependency on pyproject.toml and CHANGELOG.md formats. The workflow expects these specific files to exist and be structured conventionally for the automation to function correctly.