Back to skills
SkillHub ClubRun DevOpsFull StackDevOps

release

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.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars
5,770
Hot score
99
Updated
March 20, 2026
Overall rating
C4.8
Composite score
4.8
Best-practice grade
S96.0

Install command

npx @skill-hub/cli install brainblend-ai-atomic-agents-release

Repository

BrainBlend-AI/atomic-agents

Skill path: .claude/skills/release

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.

Open repository

Best for

Primary workflow: Run DevOps.

Technical facets: Full Stack, DevOps.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: BrainBlend-AI.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

  • Install release into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
  • Review https://github.com/BrainBlend-AI/atomic-agents before adding release to shared team environments
  • Use release for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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
---

# 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/BrainBlend-AI/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