release-manager

What This Skill Does

The Release Manager skill serves as a comprehensive DevOps command center within OpenClaw. It automates the complex lifecycle of software releases, from analyzing commit history to executing production deployments. By leveraging the Conventional Commits specification, this skill parses developer logs to determine the appropriate Semantic Version (SemVer) increment—whether it is a major architectural shift, a minor feature update, or a critical patch. It goes beyond simple versioning by offering automated changelog generation, release readiness assessments, and structured rollback planning. This ensures that every release is documented, validated, and aligned with industry-standard DevOps workflows, significantly reducing the manual overhead and human error associated with the release management lifecycle.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/alirezarezvani/release-manager Ensure you have appropriate permissions to the target repository, as the skill interacts with git logs and configuration files to perform its analysis and automation tasks.

Use Cases

1. Continuous Integration Pipeline Enhancement: Automatically generate release notes and tag versions based on daily commits.
2. Emergency Hotfix Management: Rapidly assess the scope of a critical bug and safely orchestrate a path to production.
3. Feature Rollout Coordination: Use the Release Readiness module to verify that all documentation, feature flags, and stakeholder communications are prepared before a major release.

Example Prompts

1. "Analyze the commit history since tag v1.2.0 and tell me what the next recommended version number is, assuming a major breaking change was introduced."
2. "Generate a formatted Markdown changelog based on the commits from the last week and draft a release announcement email for the stakeholders."
3. "Check the release readiness for our upcoming 2.0.0 deployment; verify that the hotfix policy is active and generate a summary checklist of tasks to complete."

Tips & Limitations

To maximize the utility of the Release Manager, ensure your team strictly adheres to the Conventional Commits format (type(scope): description). If your commit history is unformatted, the skill may struggle to accurately identify version bumps. While the skill offers powerful automation, always review the generated rollback plans before applying them in a production environment. For complex deployments involving multiple services, use the release_planner.py script to generate a granular coordination plan rather than relying on automated versioning alone.