Skip to main content
skill CX Codex

release · eigenwise — Claude Code skill: what it does, how to install

Guides publishing atomic-agents by bumping versions, building with uv, uploading to PyPI, and creating GitHub releases.

MIT ★ 6,344 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Eigenwise/atomic-agents --skill release -a claude-code
Open on GitHub

What release does

This workflow manages releases for the atomic-agents library. It validates that the local working tree is on a clean main branch, then triggers build_and_deploy.ps1. The script updates pyproject.toml, runs uv sync, builds artifacts, and pushes packages to PyPI.

Once packages are uploaded, the agent commits the modified pyproject.toml and uv.lock, pushes them upstream, and tags a release via GitHub CLI. A valid PYPI_TOKEN in .env and working PowerShell execution are required before running.

What it helps with

  • Bump version numbers according to semantic versioning rules
  • Build distribution artifacts and deploy to PyPI using uv
  • Create tagged GitHub releases using structured changelog notes

Example prompts for the agent

  • Release a patch version of atomic-agents
  • Deploy a minor release to PyPI and push the tag
  • Bump version to major and create a GitHub release

How to install release

1Skills CLI (Vercel)

npx skills add Eigenwise/atomic-agents --skill release -a claude-code

2Manually: put the files in place

~/.claude/skills/release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release

How to install release in Claude Code?

Run npx skills add Eigenwise/atomic-agents --skill release -a claude-code. The definition will be placed in ~/.claude/skills/release/SKILL.md.

What does the release skill do?

It coordinates the release lifecycle for atomic-agents: bumping version numbers, packaging via uv, publishing to PyPI, and tagging on GitHub.

What prerequisites are needed to run a release?

You must be on a clean main branch, hold write access to the repository, and supply PYPI_TOKEN in your .env file.

Source text

SKILL.md · MIT
---
name: release
description: Release a new version of atomic-agents to PyPI and GitHub. Use when the user asks to "release", "publish", "deploy", or "bump version" for atomic-agents.
allowed-tools: Read, Bash, Grep, Glob
metadata:
  internal: true
---

# Release Process for atomic-agents

## Overview

This skill guides the release process for atomic-agents, including version bumping, PyPI publishing, and GitHub release creation.

## Prerequisites

- Must be on `main` branch with clean working directory
- `.env` file must contain `PYPI_TOKEN` environment variable
- Must have push access to the repository

## Release Types

| Type | When to Use | Example |
|------|-------------|---------|
| `major` | Breaking changes | 2.5.0 → 3.0.0 |
| `minor` | New features (backwards compatible) | 2.5.0 → 2.6.0 |
| `patch` | Bug fixes only | 2.5.0 → 2.5.1 |

## Step-by-Step Process

### 1. Prepare the Branch

```bash
git checkout main
git pull
git status  # Ensure clean working directory
```

### 2. Run Build and Deploy Script

**Important**: The script bumps versions, so if it fails partway through, reset to main before retrying.

```powershell
powershell -ExecutionPolicy Bypass -File build_and_deploy.ps1 <major|minor|patch>
```

This script will:
- Read current version from `pyproject.toml`
- Increment version based on release type
- Update `pyproject.toml` with new version
- Run `uv sync` to update dependencies
- Run `uv build` to create distribution packages
- Run `uv publish` to upload to PyPI

### 3. If Script Fails - Reset and Retry

```bash
git checkout main
git reset --hard origin/main
# Fix the issue, then run script again
```

### 4. Commit and Push Version Bump

```bash
git add pyproject.toml uv.lock
git commit -m "Release vX.Y.Z"
git push
```

### 5. Create GitHub Release

```bash
gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES_HERE"
```

## Release Notes Template

```markdown
## What's New

### Feature Name
Brief description of the feature.

#### Features
- Feature 1
- Feature 2

#### Improvements
- Improvement 1

#### Bug Fixes
- Fix 1

### Full Changelog
https://github.com/eigenwise/atomic-agents/compare/vOLD...vNEW
```

## Checklist

- [ ] On main branch with clean working directory
- [ ] `.env` file has `PYPI_TOKEN`
- [ ] Determined correct release type (major/minor/patch)
- [ ] Build and deploy script completed successfully
- [ ] Version bump committed and pushed
- [ ] GitHub release created with release notes

© Eigenwise · MIT · Eigenwise/atomic-agents

Similar skills

All skills for DevOps and infrastructure →

release by other authors comes first.

release tobi A skill for Claude Code, Codex, Cursor and other IDE agents that manages project releases: validates CHANGELOG.md, updates dependencies, installs git hooks and cuts releases on command. Runs with /release 1.0.5 or /release patch. CX Codex +1 2,200installs release Yeachan-Heo A repo-aware skill that discovers release rules from CI files, caches them in .omc/RELEASE_RULE.md, and guides releases. Helpful when preparing tags and version bumps. CX Codex +1 904installs Release schpet Release is a Claude Code skill that reviews changes, updates the changelog, and publishes a version. It activates for requests to prepare or create a release. CX Codex +1 3,900installs release different-ai Cuts an OpenWork release from a git tag through GitHub Actions, with no commits to the repo. Checks open fix PRs before tagging and covers reruns after a failure. CX Codex +1 122installs release toss Automates project releases by verifying git status, bumping versions in package files, generating changelog entries, and tagging commits. CX Codex +1 208installs release-management OrchestKit release-management creates GitHub releases with gh release, picks a semver version and builds notes from merged PRs. Handy when you tag a version or publish a changelog. CX Codex +1 220installs release-notes kenryu42 release-notes updates the body of the latest GitHub Release using code diffs and merged pull requests via the gh command-line tool. CX Codex +1 ★ 2,088repo stars release-manager ruvnet release-manager coordinates release pipelines using an agent swarm. It synchronizes versions across packages, executes tests, and opens a GitHub pull request. CX Codex +1 ★ 850repo stars github-release jezweb Prepares a GitHub release by checking code for public publishing, creating a tag, and publishing through gh. Use it before making a repository public. CX Codex +1 1,400installs create-release-checklist Aaron Jacobs (@atheriel) create-release-checklist generates a release checklist for an R package and creates a corresponding GitHub issue. Useful for package maintainers preparing a new release. CX Codex +1 779installs jackin-release-notes jackin-project jackin-release-notes collects PRs since the last tag, assigns Keep a Changelog categories, and updates the [Unreleased] section in CHANGELOG.md. CX Codex +1 469installs

From the same set2

Project sponsors

Companies that keep this analytics open