release
Release preparation workflow - security audit → E2E tests → review → changelog → docs
By parcadei · 477 installs
npx skills add parcadei/continuous-claude-v3 --skill release
Source repository · Upstream listing
/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
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
Phase 2: E2E Tests
Phase 3: Final Review
Phase 4: Version Bump & Changelog
Phase 5: Release Notes
Release Types
Major Release (Breaking Changes)
Minor Release (New Features)
Patch Release (Bug Fixes)
Hotfix
Example
Blockers
The workflow stops if:
Critical security vulnerability found
E2E tests failing
Review verdict is RELEASE BLOCKED
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