Skip to main content
skill CX Codex

release · parcadei — Claude Code skill: a five-step release workflow

Runs a release through five subagents: security audit, E2E tests, final review, version bump, release notes. Useful right before a production deploy.

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

What release does

The release skill fixes the order of release prep and spawns subagents one after another. First aegis scans for dependency vulnerabilities, hardcoded secrets, SQL injection, XSS and CSRF risks, and auth problems. Then atlas runs the full E2E suite, critical path tests and integration checks.

Next review-agent reads the audit and test results, looks at commits since the last release and any breaking changes, then returns RELEASE_APPROVED or RELEASE_BLOCKED. Only after approval does herald bump the version in package.json or pyproject.toml, update version constants and write a CHANGELOG.md entry, while scribe produces RELEASE.md with features, fixes and a migration guide.

The order matters: the version bump comes after review, because breaking changes should surface first. The run stops on a critical security finding, failing E2E tests, or a RELEASE_BLOCKED verdict. --skip-security turns the audit off, and the author does not recommend it. Flags cover --major, --minor, --patch, --hotfix and --dry-run for checks without a bump.

What it helps with

  • scan dependencies and secrets before shipping
  • run the E2E suite and collect pass/fail counts
  • get a release verdict before bumping the version
  • generate a CHANGELOG.md entry and release notes
  • document breaking changes and migration steps

Example prompts for the agent

  • /release v2.0.0
  • /release --minor
  • /release --hotfix

How to install release

1Skills CLI (Vercel)

npx skills add parcadei/Continuous-Claude-v3 --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 do I install release in Claude?

Run npx skills add parcadei/Continuous-Claude-v3 --skill release -a claude-code. The skill lands in ~/.claude/skills/release/SKILL.md.

What does the release skill do?

It walks a release through five phases: security audit, E2E tests, final review, version bump with changelog, and release notes. Each phase runs as its own subagent.

What happens if the tests fail?

The workflow stops. It will not bump the version when a critical vulnerability, failing E2E tests or a RELEASE_BLOCKED verdict shows up.

Source text

SKILL.md · MIT
---
name: release
description: Release preparation workflow - security audit → E2E tests → review → changelog → docs
---

# /release - Release Workflow

Structured release preparation to ship with confidence.

## When to Use

- "Prepare a release"
- "Ship version X"
- "Release to production"
- "Cut a release"
- "Ready to deploy"
- Before any production deployment

## Workflow Overview

```
┌─────────┐    ┌─────────┐    ┌──────────────┐    ┌──────────┐    ┌─────────┐
│  aegis  │───▶│  atlas  │───▶│ review-agent │───▶│  herald  │───▶│  scribe │
│         │    │         │    │              │    │          │    │         │
└─────────┘    └─────────┘    └──────────────┘    └──────────┘    └─────────┘
  Security       E2E            Final              Version         Release
  audit          tests          review             bump            notes
```

## Agent Sequence

| # | Agent | Role | Output |
|---|-------|------|--------|
| 1 | **aegis** | Security vulnerability scan | Security report |
| 2 | **atlas** | Run full E2E test suite | Test report |
| 3 | **review-agent** | Final release review | Release approval |
| 4 | **herald** | Version bump, changelog generation | Updated version files |
| 5 | **scribe** | Release notes, documentation | RELEASE.md, docs |

## Why This Order?

1. **Security first**: Catch vulnerabilities before they ship
2. **E2E tests**: Verify full system works end-to-end
3. **Final review**: Human-in-the-loop approval
4. **Version bump**: Only after approval
5. **Documentation**: Ship with proper release notes

## Execution

### Phase 1: Security Audit

```
Task(
  subagent_type="aegis",
  prompt="""
  Security audit for release: [VERSION]

  Scan for:
  - Dependency vulnerabilities (npm audit, pip audit)
  - Hardcoded secrets/credentials
  - SQL injection, XSS, CSRF risks
  - Authentication/authorization issues
  - Insecure configurations

  Output: Security report with severity levels
  """
)
```

### Phase 2: E2E Tests

```
Task(
  subagent_type="atlas",
  prompt="""
  Run E2E tests for release: [VERSION]

  Execute:
  - Full E2E test suite
  - Critical path tests
  - Integration tests
  - Performance benchmarks (if applicable)

  Output: Test report with pass/fail counts
  """
)
```

### Phase 3: Final Review

```
Task(
  subagent_type="review-agent",
  prompt="""
  Final release review: [VERSION]

  Review:
  - Security audit results
  - E2E test results
  - Changes since last release (git log)
  - Breaking changes
  - Migration requirements

  Output: RELEASE_APPROVED or RELEASE_BLOCKED with reasons
  """
)
```

### Phase 4: Version Bump & Changelog

```
Task(
  subagent_type="herald",
  prompt="""
  Prepare release: [VERSION]

  Tasks:
  - Bump version in package.json/pyproject.toml
  - Generate CHANGELOG.md entry
  - Update version constants in code
  - Tag commit (don't push yet)

  Follow semantic versioning.
  """
)
```

### Phase 5: Release Notes

```
Task(
  subagent_type="scribe",
  prompt="""
  Write release notes: [VERSION]

  Include:
  - Summary of changes
  - New features
  - Bug fixes
  - Breaking changes
  - Migration guide (if needed)
  - Contributors

  Output: RELEASE.md or update docs
  """
)
```

## Release Types

### Major Release (Breaking Changes)
```
/release --major
→ Full workflow with migration guide
```

### Minor Release (New Features)
```
/release --minor
→ Full workflow, lighter security review
```

### Patch Release (Bug Fixes)
```
/release --patch
→ Security + tests + quick review
```

### Hotfix
```
/release --hotfix
→ Expedited: aegis → atlas → herald
```

## Example

```
User: /release v2.0.0

Claude: Starting /release workflow for v2.0.0...

Phase 1: Security audit...
[Spawns aegis]
✅ No critical vulnerabilities
⚠️ 2 low-severity issues (documented)

Phase 2: E2E tests...
[Spawns atlas]
✅ 156/156 E2E tests passing

Phase 3: Final review...
[Spawns review-agent]
✅ RELEASE_APPROVED
- 47 commits since v1.9.0
- 3 new features
- 12 bug fixes
- No breaking changes

Phase 4: Version bump...
[Spawns herald]
✅ Version bumped to 2.0.0
✅ CHANGELOG.md updated
✅ Git tag created

Phase 5: Release notes...
[Spawns scribe]
✅ RELEASE-v2.0.0.md created

┌─────────────────────────────────────────┐
│ Release v2.0.0 Ready                    │
├─────────────────────────────────────────┤
│ Security: ✅ Passed                     │
│ Tests: ✅ 156/156                       │
│ Review: ✅ Approved                     │
│                                         │
│ Next steps:                             │
│ 1. git push origin v2.0.0              │
│ 2. Create GitHub release               │
│ 3. Deploy to production                │
└─────────────────────────────────────────┘
```

## Blockers

The workflow stops if:
- Critical security vulnerability found
- E2E tests failing
- Review verdict is RELEASE_BLOCKED

```
Phase 1: Security audit...
❌ CRITICAL: SQL injection in user.py:45

Release blocked. Fix critical issues before proceeding.
```

## Flags

- `--major/--minor/--patch`: Semantic version type
- `--hotfix`: Expedited release path
- `--skip-security`: Skip security audit (not recommended)
- `--dry-run`: Run checks without bumping version

© parcadei · MIT · parcadei/Continuous-Claude-v3

Similar skills

Everything for DevOps and infrastructure →

release by other authors comes first.

release tobi This skill manages a project release by checking the changelog, installing git hooks, and updating release versions. Use it when the project has a defined release flow. 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 832installs release cyrusagents This skill walks a Cyrus CLI release through trusted publishing: prepare, verify, publish, finish. Useful when a version has to ship without touching packages by hand. CX Codex +1 829installs release modelcontextprotocol Walks one milestone release from the release issue through audit, version bumps and the merge PR to the GitHub Release a maintainer publishes. CX Codex +1 ★ 91,547repo stars release-skills JimLiu Automates release workflows, conventional commit parsing, and version bumps for Node.js, Python, or Rust. Builds changelogs and creates GitHub Releases. CX Codex +1 25,600installs cmux-release manaflow-ai Automates the cmux release pipeline by extracting changelog lines from pull requests, bumping versions, and running safety checks. CX Codex +1 4,700installs github-release-management ruvnet Automates GitHub releases: drafts, changelogs, builds, multi-target deploys. Handy when releases ship often and manual steps eat the afternoon. CX Codex +1 1,200installs utility-pm-release-conductor product-on-purpose Walks a pm-skills release through six gates: readiness, adversarial review, version bump, tag and post-tag hygiene. Refuses gate bypasses. CX Codex +1 595installs jackin-release-check jackin-project Runs the jackin❯ release-readiness gates and reports a verdict for each one. Use it before cutting a release. CX Codex +1 469installs re0-release LilMGenius Walks a pending change through the repo's shipping and releasing checklist, then tags and publishes once you confirm. Run it by hand when you've decided to ship. CX Codex +1 1,200installs

From the same set69

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor