publish-python-release

A release workflow for building or publishing Python packages through a repository's GitHub Actions setup. A Python distribution is a package format, such as a wheel or source archive, that can be installed or uploaded to PyPI.

In plain words
What is it for?
Use it to build temporary or matrix-tested packages, publish an authorized release to PyPI, create a release tag, or troubleshoot the publishing workflow.
Why use it?
It keeps development builds, tests, official releases, tags, and publishing aligned with the repository's defined process.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nvidia-nemo/switchyard/publish-python-release
Any agent
npx skills add NVIDIA-NeMo/Switchyard --skill publish-python-release
Clone the repo
git clone --depth 1 https://github.com/NVIDIA-NeMo/Switchyard

Made for: Claude Code, Codex.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 560 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.00560
Opus 5 $0.00028 $0.00280
Sonnet 5 $0.00011 $0.00112
Haiku 4.5 $0.00006 $0.00056

Measured yesterday against content hash 935ac24fe09f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

publish-python-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/publish-python-release/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publish The Python Package

Use .github/workflows/publish.yml as the source of truth. The supporting runbook is docs/internal/release_workflow.md.

Release Paths

Intent Trigger Result
One temporary wheel Manual dispatch with build_dev_artifact=true Linux x86_64 GitHub artifact, retained for one day
Full matrix test Manual dispatch with build_dev_matrix=true sdist and wheel artifacts; no publish
Official release Push vMAJOR.MINOR.PATCH matching pyproject.toml Full matrix, PyPI publish, GitHub Release

Manual builds are artifact-only. Official releases use PyPI Trusted Publishing through the GitHub environment named pypi; do not add a long-lived PyPI token.

Workflow

  1. Read the current workflow and pyproject.toml; do not rely on remembered inputs or versions.
  2. Confirm the requested version and whether the user explicitly authorized creating a tag.
  3. For workflow changes, run the focused release-helper tests and inspect the workflow diff.
  4. Dispatch a development build or push the authorized release tag.
  5. Monitor every matrix job and verify the resulting package from a clean temporary environment.

Example development dispatch:

gh workflow run publish.yml \
  -f build_dev_artifact=true \
  -f build_dev_matrix=false \
  -f dev_version=0.0.1.dev0

Guardrails

  • Never create or push a tag unless the user explicitly requested it.
  • Never publish a manual development build to PyPI.
  • Never reuse a deleted PyPI filename or version; PyPI permanently reserves filenames.
  • Keep release versions consistent across the tag, pyproject.toml, and package metadata.
  • Verify installation outside the checkout so local imports cannot mask packaging defects.
  • Cargo crate publishing is a separate manual workflow. Inspect each crate's Cargo.toml, dependency publication order, and crates.io ownership before running cargo publish.

Release-Infrastructure Validation

uv run ruff check scripts/release/set_dev_wheel_version.py tests/test_dev_wheel_versioning.py
uv run pytest tests/test_dev_wheel_versioning.py -v
python scripts/release/set_dev_wheel_version.py 0.0.1.dev0 --print-version
git diff --check

Read the full file on GitHub · 57 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 57 lines · 55 tokens per session scan A 935ac24fe09f

Subscribe to this mod's changes

publish-python-release is a skill published in the GitHub repository NVIDIA-NeMo/Switchyard (2,588 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 560 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens