Release
Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows.
npx -y skills add parcadei/Continuous-Claude-v3 --skill releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Release preparation workflow - security audit → E2E tests → review → changelog → docs
SKILL.md
5.7 KB, as published. Nobody here has run it
/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?
- Security first: Catch vulnerabilities before they ship
- E2E tests: Verify full system works end-to-end
- Final review: Human-in-the-loop approval
- Version bump: Only after approval
- 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
Gives 0 of the 12 instructions most ship operate skills give
Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-06
- document a rollback plan before deploymentin 40 of 779, across 21 files
- create an annotated git tagin 21 of 779, across 20 files
- Run the test suitein 20 of 779
- update the changelogin 20 of 779, across 18 files
- verify deployment health after launchin 19 of 779, across 10 files
- clean up feature flags after full rolloutin 18 of 779, across 10 files
- verify the working tree is cleanin 18 of 779
- test both feature flag statesin 17 of 779, across 9 files
- Make database migrations backward-compatiblein 16 of 779, across 8 files
- set up error monitoring before launchin 15 of 779, across 7 files
- monitor metrics at each rollout stagein 14 of 779, across 5 files
- create a github releasein 14 of 779
Said here and by no other author read
- run security audit first
- run full E2E test suite
- perform final release review
- bump version after approval
- follow semantic versioning
- do not push git tag yet
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.