Menu
Release workflow for version bumping, changelog generation, and deployment preparation. Coordinates release across all domains.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate customized .claude/ harness framework with Fusion Architecture (GAN-inspired + Domain Specialists). TRIGGER when user wants to set up AI-assisted development structure, create a new project harness, add structure to existing projects, or mentions 'harness', 'scaffold', 'framework setup'. Supports all domains through template + dynamic generation.
Negotiates 'done' criteria between Generator, Evaluator, and architect-lead before implementation begins. Converts subjective goals into testable, gradable criteria with clear domain responsibilities.
Guided database migration workflow — from schema design to rollback documentation.
Production incident response workflow — triage, root cause analysis, and resolution.
Track, categorize, and prioritize technical debt across the codebase.
Save current progress with structured handoff artifact. Enables context reset for long-running tasks and session recovery.
| name | release |
| description | Release workflow for version bumping, changelog generation, and deployment preparation. Coordinates release across all domains. |
| user-invocable | true |
You are facilitating the Release process. Your role is to coordinate version bumping, changelog generation, and deployment preparation.
Release workflow ensures:
RELEASE REQUEST -> VERSION DECISION -> CHANGELOG -> PRE-RELEASE TESTS -> TAG -> DEPLOY PREP -> ANNOUNCE
| Change Type | Version Bump | Example |
|---|---|---|
| Breaking API change | Major | 1.0.0 -> 2.0.0 |
| New feature | Minor | 1.0.0 -> 1.1.0 |
| Bug fix | Patch | 1.0.0 -> 1.0.1 |
Run full test suite:
Prepare deployment:
Create release announcement:
# Release: v[VERSION]
**Date**: [Date]
**Type**: Major | Minor | Patch
**Previous Version**: v[PREV]
---
## Summary
[2-3 sentence summary of this release]
---
## Changelog
### Breaking Changes
- [Breaking change 1]
- [Breaking change 2]
### Features
- [Feature 1]
- [Feature 2]
### Fixes
- [Fix 1]
- [Fix 2]
### Dependencies
- [Dependency update 1]
### Documentation
- [Doc update 1]
---
## Migration Guide
[If breaking changes, provide migration steps]
### Step 1: [Description]
```bash
[command]
[instructions]
| Domain | Files Changed |
|---|---|
| Frontend | [count] |
| Backend | [count] |
| Database | [count] |
| DevOps | [count] |
| Category | Status |
|---|---|
| Unit Tests | PASS/FAIL |
| Integration Tests | PASS/FAIL |
| E2E Tests | PASS/FAIL |
| Coverage | [percentage]% |
If issues occur:
## Version Files to Update
| File | Format | Location |
|------|--------|----------|
| package.json | "version": "x.x.x" | Frontend |
| pyproject.toml | version = "x.x.x" | Backend |
| __init__.py | __version__ = "x.x.x" | Backend |
| docker-compose.yml | image: app:x.x.x | DevOps |
## Changelog Categories
### Breaking Changes
- API endpoint removed/changed
- Authentication flow changed
- Database schema incompatible
- Configuration format changed
### Features
- New endpoint
- New component/page
- New configuration option
- Performance improvement
### Fixes
- Bug resolved
- Error handling improved
- Security vulnerability patched
- Performance regression fixed
### Dependencies
- Package upgraded
- Package added
- Package removed
### Documentation
- API docs updated
- README updated
- Architecture docs updated
## Pre-Release Checklist
- [ ] All tests pass
- [ ] No regressions detected
- [ ] Coverage at target
- [ ] Security scan clean
- [ ] Documentation updated
- [ ] Changelog complete
- [ ] Version bumped in all files
- [ ] Tag created
## Post-Release Checklist
- [ ] Tag pushed to remote
- [ ] Staging deployed
- [ ] Smoke tests pass
- [ ] Production deployed
- [ ] Monitoring verified
- [ ] Announcement sent
## Anti-Patterns to Avoid
- Releasing without passing tests
- Missing changelog entries
- Breaking changes without migration guide
- Version bump in wrong files
- Releasing on Friday
## Usage
/release [type]
Example:
/release minor /release patch
## Coordination
- architect-lead approves all releases
- Domain leads approve domain changes
- All tests must pass before release
- Breaking changes require migration documentation