release
SolidRelease preparation workflow - security audit → E2E tests → review → changelog → docs
AI & Automation 552 stars
45 forks Updated 6 days ago MIT
Install
Quality Score: 91/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# /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
### Pha...
Details
- Author
- vibeeval
- Repository
- vibeeval/vibecosystem
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Featured
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs
3,951 Updated 2 days ago
parcadei AI & Automation Listed
release
Prepare a release for the owner to ship - verify the readiness list mechanically, then assemble the changelog, semver proposal, and release notes into the filled RELEASE-TEMPLATE, ending at a proposal entry on DECISIONS.md. Owner/CEO invoked only. Use when the user says /release, "prepare a release", "cut a release", or "are we ready to ship". It NEVER tags, publishes, or deploys - deploy is a manual owner step, always.
8 Updated 2 months ago
devmesh-in AI & Automation Listed
release
Release preparation and publishing
11 Updated today
Smart-AI-Memory