release-pycel2sql

Automate version tagging, building, and publishing to PyPI for pycel2sql.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of cutting new releases for the pycel2sql package by performing version tagging, building, and publishing to PyPI.

Core Features & Use Cases

  • Release Validation: Validates the working tree before tagging, ensuring a clean and in-sync state.
  • Version Tagging: Tags new versions with semantic versioning (SemVer), following patch, minor, or major updates as needed.
  • Building and Publishing: Builds source distributions and wheels, and publishes them to PyPI via OIDC trusted publishing.
  • Use Case: Streamline the release process of the pycel2sql package by automating the tasks involved in cutting and shipping new versions.

Quick Start

Run the skill by checking out the 'main' branch, executing the preflight checks, and then creating a tag for the new release. Use the following commands as a guide:

git checkout main && git pull --ff-only origin main
bash .claude/skills/release-pycel2sql/scripts/release_preflight.sh

Frequently Asked Questions about release-pycel2sql

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

FAQPage Schema
How do I automate Python package publishing to PyPI using CI/CD?

Automate Python package publishing by integrating a release management workflow that performs preflight checks, tags versions, builds distributions, and publishes to PyPI using OIDC trusted publishing within a CI/CD pipeline.

How does semantic versioning work when cutting a new release tag in git?

Semantic versioning tags new releases as patch, minor, or major updates based on the changes introduced, ensuring the package version accurately reflects the scope of the modification before building distributions.

What preflight checks are needed before tagging a software release?

Preflight checks validate the git working tree before tagging, ensuring the repository is clean and the local branch is fully synchronized with the remote main branch to prevent releasing uncommitted or outdated code.

Can I use OIDC trusted publishing to publish to PyPI from a CI/CD pipeline?

Yes, OIDC trusted publishing is used to securely publish source distributions and wheels to PyPI directly from the CI/CD pipeline without requiring long-lived API tokens.

What is the best way to build source distributions and wheels for a Python package release?

The best way is to run an automated release script that checks out the main branch, executes preflight validation, applies a semantic version git tag, and then builds the source distributions and wheels.

Why does my automated package release fail during version tagging?

Automated release tagging fails if the preflight checks detect a dirty working tree or if the local main branch is not synchronized with the remote repository, preventing the creation of an invalid release tag.