The Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
The Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases.
The Release Manager skill provides comprehensive tools and knowledge for managing software releases end-to-end. From parsing conventional commits to generating changelogs, determining version bumps, and orchestrating release processes, this skill ensures reliable, predictable, and well-documented software releases.
Core Capabilities
Automated Changelog Generation from git history using conventional commits
Semantic Version Bumping based on commit analysis and breaking changes
Release Readiness Assessment with comprehensive checklists and validation
Release Planning & Coordination with stakeholder communication templates
Rollback Planning with automated recovery procedures
Hotfix Management for emergency releases
Feature Flag Integration for progressive rollouts
Key Components
Scripts
changelog_generator.py - Parses git logs and generates structured changelogs
version_bumper.py - Determines correct version bumps from conventional commits
release_planner.py - Assesses release readiness and generates coordination plans
feat: A new feature (correlates with MINOR version bump)
fix: A bug fix (correlates with PATCH version bump)
docs: Documentation only changes
style: Changes that do not affect the meaning of the code
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools
ci: Changes to CI configuration files and scripts
build: Changes that affect the build system or external dependencies
breaking: Introduces a breaking change (correlates with MAJOR version bump)
Examples
feat(user-auth): add OAuth2 integration
fix(api): resolve race condition in user creation
docs(readme): update installation instructions
feat!: remove deprecated payment API
BREAKING CHANGE: The legacy payment API has been removed
Automated Changelog Generation
Changelogs are automatically generated from conventional commits, organized by:
Structure
# Changelog## [Unreleased]### Added### Changed ### Deprecated### Removed### Fixed### Security## [1.2.0] - 2024-01-15### Added- OAuth2 authentication support (#123)
- User preference dashboard (#145)
### Fixed- Race condition in user creation (#134)
- Memory leak in image processing (#156)
### Breaking Changes- Removed legacy payment API
Grouping Rules
Added for new features (feat)
Fixed for bug fixes (fix)
Changed for changes in existing functionality
Deprecated for soon-to-be removed features
Removed for now removed features
Security for vulnerability fixes
Metadata Extraction
Link to pull requests and issues: (#123)
Breaking changes highlighted prominently
Scope-based grouping: auth:, api:, ui:
Co-authored-by for contributor recognition
Version Bump Strategies
Version bumps are determined by analyzing commits since the last release:
Automatic Detection Rules
MAJOR: Any commit with BREAKING CHANGE or ! after type
MINOR: Any feat type commits without breaking changes
Forward-only migrations preferred (add columns, not drop)
Infrastructure Rollback:
Blue-green deployment switch
Load balancer configuration revert
DNS changes (longer propagation time)
Automated Rollback
# Example rollback automationdefmonitor_deployment():
if error_rate() > THRESHOLD:
alert_oncall("Error rate spike detected")
if auto_rollback_enabled():
execute_rollback()
Release Metrics & Analytics
Key Performance Indicators
Lead Time: From commit to production
Deployment Frequency: Releases per week/month
Mean Time to Recovery: From incident to resolution
Change Failure Rate: Percentage of releases causing incidents
Quality Metrics
Rollback Rate: Percentage of releases rolled back
Hotfix Rate: Hotfixes per regular release
Bug Escape Rate: Production bugs per release
Time to Detection: How quickly issues are identified
Process Metrics
Review Time: Time spent in code review
Testing Time: Automated + manual testing duration
Approval Cycle: Time from PR to merge
Release Preparation: Time spent on release activities
Tool Integration
Version Control Systems
Git: Primary VCS with conventional commit parsing
GitHub/GitLab: Pull request automation and CI/CD
Bitbucket: Pipeline integration and deployment gates
CI/CD Platforms
Jenkins: Pipeline orchestration and deployment automation
GitHub Actions: Workflow automation and release publishing
GitLab CI: Integrated pipelines with environment management
CircleCI: Container-based builds and deployments
Monitoring & Alerting
DataDog: Application performance monitoring
New Relic: Error tracking and performance insights
