skills.rest
andrewendlinger
andrewendlingerCOMMUNITY
Explore all skills by this author →
GitHub

release

Orchestrate xmris releases from preflight checks to PyPI publication.

5|1|Updated Feb 18, 2026
Search Tags:#publishing#github actions#release#pypi#version bump#ci pipeline
One-click install
npx skills add https://github.com/andrewendlinger/xmris --skill release-andrewendlinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/andrewendlinger/xmris/tree/main/.claude/skills/release
Command: npx skills add https://github.com/andrewendlinger/xmris --skill release-andrewendlinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides a controlled xmris release process so you can validate the full test matrix before versioning, avoid broken releases, and publish to PyPI only after the merged commit is ready.

Core Features & Use Cases

  • Release branch workflow: Run the full cross-platform CI matrix on an unbumped release branch before changing the version.
  • Version bump and merge discipline: Bump the version only after tests are green, then land it through a pull request on main.
  • Automated publishing: Tag the merged commit on main to trigger GitHub Actions and Trusted Publishing to PyPI.
  • Use Case: A maintainer preparing a patch, minor, or major release follows the checklist to confirm CI, cut the release branch, merge the version bump, and publish the tagged release.

Quick Start

Use the release skill to prepare the next xmris release for version 0.7.0 and walk me through the preflight checks, branch workflow, merge, and tag publishing steps.

Frequently Asked Questions about release

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

FAQPage Schema
How do I safely publish a Python package to PyPI using GitHub Actions and tag-triggered trusted publishing?▼

To publish to PyPI safely, you should validate cross-platform CI on an unbumped release branch, merge the version bump via a pull request to main, and tag the merged commit to trigger GitHub Actions trusted publishing. This prevents broken releases.

What's the best way to manage a version bump and release branch workflow before deploying to PyPI?▼

The best way to manage a version bump is to cut a release branch, run the full cross-platform CI matrix before changing the version, and only bump the version after tests pass. The bump is then merged to main through a pull request.

Do I need GitHub CLI and uv to automate a tag-triggered PyPI release pipeline?▼

Yes, you need GitHub CLI, uv, and git installed to automate a tag-triggered PyPI release. These tools verify repository status, execute the version bump, create pull requests, and publish the merged release commit.

Why should I run cross-platform CI validation before bumping the version for a PyPI release?▼

You should run cross-platform CI validation before bumping the version to ensure the full test matrix passes on an unbumped release branch. This avoids versioning broken code and ensures the merged commit is ready for publication.

Can I use a branch-based release management workflow to prevent broken PyPI publications?▼

Yes, using a branch-based release management workflow prevents broken PyPI publications by isolating version bumps and requiring cross-platform CI validation before merging the version change to main and triggering the tag-based publication.

Related Skills

Explore More Software Engineering Skills→
glwrglwr
1

release

Prepare and publish an Apple app release with versioning and GitHub release creation.

Community
Advanced
trotsky1997trotsky1997
6

pypi-publisher

Automates the PyPI publishing workflow for Python packages.

Community
Advanced
VanLVanL
1

ship

Automate branch detection, testing, version management, and pull request creation.

Community
Intermediate
xz1220xz1220

release

Analyze version sources and CI rules to orchestrate repository releases.

Community
Advanced