when-releasing-software-use-github-release-management
Automate software releases with AI agents
Software releases require coordinating version bumps, testing, deployment, and documentation. This skill orchestrates multiple AI agents to handle the entire release workflow automatically. It ensures consistent processes, reduces human error, and provides rollback capabilities.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"when-releasing-software-use-github-release-management" ์ฌ์ฉ ์ค์ ๋๋ค. Release version 1.5.0 using the standard workflow
์์ ๊ฒฐ๊ณผ:
- Release Manager initialized with 5 agents
- Version determined: 1.5.0 (minor bump for new features)
- Release branch created: release/v1.5.0
- Staging deployment successful
- All 47 tests passed in validation suite
- Security review completed with no critical findings
- Changelog generated with 3 features and 5 bug fixes
- Draft release created on GitHub
- Go/no-go decision: PROCEED
- Production deployment started using rolling strategy
- Deployment healthy - 100 percent rollout complete
- Release published on GitHub
- Release branch merged to main
"when-releasing-software-use-github-release-management" ์ฌ์ฉ ์ค์ ๋๋ค. Create an emergency hotfix for a critical production bug
์์ ๊ฒฐ๊ณผ:
- Hotfix branch created from v1.4.2 tag
- Fast-track security review completed
- Version bumped to 1.4.3-hotfix.1
- Targeted regression tests passed
- Emergency approval granted
- Hotfix deployed to production immediately
- Hotfix backported to main and develop branches
- Post-incident documentation created
"when-releasing-software-use-github-release-management" ์ฌ์ฉ ์ค์ ๋๋ค. Rollback deployment due to high error rate
์์ ๊ฒฐ๊ณผ:
- Error rate spike detected: 7 percent (threshold exceeded)
- Rollback decision: TRIGGER
- Previous version v1.4.2 redeployed
- Rollback validation: All smoke tests passed
- Error rates normalized to 0.2 percent
- Post-mortem scheduled for incident review
- Action items created to prevent recurrence
๋ณด์ ๊ฐ์ฌ
์์ This skill contains only documentation and workflow descriptions - no executable code exists. All referenced scripts (semver.sh, deploy.sh, etc.) are documentation placeholders. Static analysis flagged patterns like shell backticks and cryptographic algorithms because it cannot distinguish between example documentation and actual code. The skill-report.json confirms safe: risk_level is 'safe', is_blocked is false, and safe_to_publish is true. This is a pure prompt engineering skill.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (88)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Standard Release Orchestration
Automate major, minor, and patch releases with full testing, staging validation, and production deployment.
Hotfix Emergency Response
Fast-track critical production fixes with expedited approval process and immediate deployment.
Rollback Management
Monitor deployments and automatically trigger rollback when health metrics exceed thresholds.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Use the GitHub release management skill to release version 2.1.0. Run through the standard release workflow with staging validation and production deployment.
Use the GitHub release management skill to create a hotfix for a critical production bug. Fast-track the approval and deploy immediately.
Deploy the new release using a rolling strategy. Monitor health metrics and be ready to rollback if error rate exceeds 5 percent.
Deploy the release using canary strategy at 10 percent traffic. Gradually increase to 25 percent, then 50 percent, then full rollout.
๋ชจ๋ฒ ์ฌ๋ก
- Run staging validation before any production deployment to catch 80 percent of issues early
- Use canary or rolling deployments for major releases to minimize blast radius
- Always test rollback procedures before production deployment
ํผํ๊ธฐ
- Skipping validation tests to meet release deadlines
- Deploying without monitoring and health checks configured
- Releasing without changelog or release notes documentation
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What AI tools support this skill?
Does this skill deploy to any hosting platform?
How does rollback work?
Is my repository data safe?
What if tests fail during release?
How is this different from GitHub Actions?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
ํ์ผ ๊ตฌ์กฐ
๐ release-management-process.dot
๐ SKILL.md