Release

作者 parcadeid07ff4b06b62無授權條款3.9K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫8 個月前更新

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

僅含說明DevOps & Cloud
AI 產生的概覽

結構化的發布準備工作流程:安全稽核、端對端測試、審查、版本號更新、變更記錄與發行說明。

功能
這個技能定義了一套分五個階段依序執行的發布準備流程:安全弱點掃描、完整端對端測試套件、最終發布審查、版本號更新與變更記錄產生,以及發行說明與文件。每個階段都委派給指定的子代理(aegis、atlas、review-agent、herald、scribe),並附上明確的提示詞與產出物,例如安全報告、測試報告、核准結論、更新後的版本檔案或 RELEASE.md。它也說明了發布類型(major、minor、patch、hotfix)、會中止流程的阻擋條件,以及 --dry-run、--skip-security 等參數。
適用情境
適用於準備發布某個版本、切出發布版本或部署到正式環境,並希望在發布前執行一套可重複、有順序的檢查清單時。適合「準備發布」「發布版本 X」「可以部署了」這類請求。
執行需求
僅為說明性指示,不隨附指令碼。它假定存在指定的子代理(aegis、atlas、review-agent、herald、scribe),且專案具備測試套件、package.json 或 pyproject.toml 等版本檔案,以及可供產生變更記錄的 git 歷史。

/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

#AgentRoleOutput
1aegisSecurity vulnerability scanSecurity report
2atlasRun full E2E test suiteTest report
3review-agentFinal release reviewRelease approval
4heraldVersion bump, changelog generationUpdated version files
5scribeRelease notes, documentationRELEASE.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

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

來源與署名

來源:parcadei/continuous-claude-v3位於.claude/skills/release提交d07ff4b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架