Install
mkdir -p .claude/skills/release-dantsai0903 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16534" && unzip -o skill.zip -d .claude/skills/release-dantsai0903 && rm skill.zipInstalls to .claude/skills/release-dantsai0903
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guide the release procedure for namingpaper - version bump, commit, GitHub release, and PyPI publish.Key capabilities
- →Bump version numbers in `pyproject.toml` and `src/namingpaper/__init__.py`
- →Commit and push version bump changes to `main`
- →Create a GitHub release with a specified title and notes
- →Build and publish the package to PyPI
- →Clean old distribution files before building
- →Confirm version number and release type with the user
How it works
The skill guides the user through the `namingpaper` release procedure, which involves updating version files, committing changes, creating a GitHub release, and publishing the package to PyPI. It ensures proper versioning and artifact management.
Inputs & outputs
When to use release
- →Release a new namingpaper version
- →Publish to PyPI
- →Create a GitHub release for namingpaper
About this skill
Release Procedure
Follow these steps to release a new version of namingpaper. The user should provide the version number (X.Y.Z).
Steps
- Bump version in both
pyproject.tomlandsrc/namingpaper/__init__.py - Commit and push:
git add -A && git commit -m "Bump version to X.Y.Z" && git push origin main - Create GitHub release:
gh release create vX.Y.Z --title "vX.Y.Z" --prerelease --notes "..."- Drop
--prereleasefor stable releases
- Drop
- Build and publish to PyPI:
uv build source .env # contains UV_PUBLISH_TOKEN uv publish --token "$UV_PUBLISH_TOKEN" - Clean old dists if needed:
rm -rf dist/before building to avoid uploading stale files
Important
- Always confirm the version number with the user before starting.
- Ask whether this is a stable or prerelease before creating the GitHub release.
When not to use it
- →When the user does not provide the version number
- →When the user does not specify if it's a stable or prerelease
- →When releasing a package other than `namingpaper`
Limitations
- →Requires the user to provide the version number (X.Y.Z)
- →Requires confirmation on whether the release is stable or prerelease
- →Requires `UV_PUBLISH_TOKEN` to be sourced from `.env` for PyPI publishing
How it compares
This skill provides a specific, step-by-step release procedure for the `namingpaper` package, including GitHub and PyPI interactions, unlike a generic version control or build tool.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 5mo | Review | Beginner |
| publish-pypi | 1 | 6mo | Review | Intermediate |
| release-bump | 0 | 5mo | No flags | Intermediate |
| build-release | 0 | 1mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
publish-pypi
wandb
Build and publish the Weave Python SDK to PyPI. Use when releasing a new version.
release-bump
himatts
Prepare versioned release updates for Lime Pipeline. Use when user-visible behavior changes require bumping `bl_info["version"]`, updating `CHANGELOG.md`, and producing release-ready QA notes.
build-release
tsilva
Launch and monitor a SuperMarioBros-Nes-turbo PyPI release. Use when the user says /build-release, asks to cut a release, asks to tag/publish a version, asks whether a release made it to PyPI, or asks for macOS and Linux supermariobrosnes-turbo wheels.
azure-functions
aj-geddes
Create serverless functions on Azure with triggers, bindings, authentication, and monitoring. Use for event-driven computing without managing infrastructure.
ml-pipeline-workflow
wshobson
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
ollama-setup
jeremylongshore
Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.