release

Solid

Release preparation workflow - security audit → E2E tests → review → changelog → docs

AI & Automation 501 stars 42 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

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
3 months ago
Last Updated
2 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category