publish-pip

Automate Python package versioning, build artifacts, and dual-name PyPI distribution.

8|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/HumanBean17/jrag --skill publish-pip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-pip
Source: https://github.com/HumanBean17/jrag/tree/main/.claude/skills/publish-pip
Command: npx skills add https://github.com/HumanBean17/jrag --skill publish-pip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires build, twine, certifi, and includes scripts (resource) components.

What problem does it solve?

This skill automates the complex, multi-step process of publishing the jrag-cli package to PyPI, ensuring that both the current and legacy package names are kept in sync to prevent user disruption.

Core Features & Use Cases

  • Dual-Package Synchronization: Automatically handles the build and upload process for both jrag-cli and java-codebase-rag to ensure legacy users remain supported.
  • Safety Guardrails: Performs automated version checks and artifact validation to prevent the accidental upload of stale or mismatched build files.
  • Use Case: When you need to release a new version of the CLI, this skill manages the version bump, artifact cleanup, build verification, and dual-upload process in one controlled workflow.

Quick Start

Use the publish-pip skill to bump the version and release the latest updates to both PyPI project names.

Frequently Asked Questions about publish-pip

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

FAQPage Schema
How do I automate Python package publishing to multiple PyPI project names?

Automating Python package publishing to multiple PyPI project names requires a workflow that manages version bumping, artifact generation, and synchronized uploads. This skill handles that end-to-end release process to ensure dual-name distribution remains in sync without manual intervention.

How does dual-package synchronization prevent user disruption during PyPI releases?

Dual-package synchronization prevents disruption by building and uploading artifacts for both current and legacy package names in a single controlled workflow. This ensures users relying on either identifier receive the synchronized update simultaneously.

What is the best way to add safety guardrails for PyPI release uploads?

The best way to add safety guardrails for PyPI release uploads is to perform automated version checks and artifact validation before distribution. This prevents the accidental upload of stale or mismatched build files to the registry.

Do I need twine and certifi to securely distribute Python packages to PyPI?

Yes, you need twine and certifi to securely distribute Python packages to PyPI. Twine handles the authenticated upload process while certifi provides the certificate validation required for verified and secure distribution.

Can I use build and twine for automated version bumping and artifact cleanup?

Yes, you can use build and twine for automated version bumping and artifact cleanup. The build tool generates the distribution artifacts while twine manages the upload, and the workflow automates the cleanup of stale files before generation.