skills.rest
jenkinsm13
jenkinsm13COMMUNITY
Explore all skills by this author →
GitHub

publish

Automate Python package releases by bumping versions, building artifacts, and publishing to PyPI.

3|Updated Feb 22, 2026
Search Tags:#automation#git#versioning#release#pypi#publish
One-click install
npx skills add https://github.com/jenkinsm13/resolve-mcp --skill publish-jenkinsm13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/jenkinsm13/resolve-mcp/tree/main/.claude/skills/publish
Command: npx skills add https://github.com/jenkinsm13/resolve-mcp --skill publish-jenkinsm13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire process of releasing a new version of the package, from version bumping to pushing to GitHub.

Core Features & Use Cases

  • Version Management: Automatically increments the patch version in pyproject.toml.
  • Build & Publish: Creates distributable packages (sdist and wheel) and uploads them to PyPI.
  • Code Commit: Commits the version changes with a clear release message and pushes to the main branch.
  • Use Case: When you've completed a new set of features and bug fixes, you can run this Skill to prepare and deploy a new version of your library without manual steps.

Quick Start

Run /publish to release the current version.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate publishing a Python package to PyPI?▼

To automate publishing a Python package to PyPI, this skill bumps the patch version in pyproject.toml, builds sdist and wheel artifacts, uploads them to PyPI, and pushes the changes to GitHub.

Can I do a minor or major version bump instead of a patch version?▼

Yes, minor or major version bumps are supported. While the process defaults to incrementing the patch version in pyproject.toml, it supports optional minor or major version bumps for releases.

What is the best way to release a new version of a library and push to GitHub?▼

The best way to release a new library version is to automate the workflow: bump the version in pyproject.toml, build distribution packages, publish to PyPI, commit the changes, and push to the main GitHub branch.

Does the release process commit version changes back to Git?▼

Yes, the release process commits version changes back to Git. It commits the updated pyproject.toml with a clear release message and pushes the commit directly to the main branch on GitHub.

Do I need to manually build sdist and wheel files before publishing to PyPI?▼

No, you do not need to manually build sdist and wheel files. The release automation creates the distributable packages for you before uploading them directly to PyPI.

Related Skills

Explore More Software Engineering Skills→
JhabbigJhabbig

python-packaging

Create Python package metadata and project structure with pyproject.toml.

Community
Advanced
deandumdeandum
3

ops/release

Automate version decisions, tag creation, changelog generation, and GitHub Releases.

Community
Advanced
holger1411holger1411
70

qa

Run lint, format, TypeScript, and build checks on AstroDeck projects.

Community
Advanced
databrickslabsdatabrickslabs
60

build_connector_package

Create a pyproject.toml file and build a source connector as a Python package.

Official
Intermediate