Can I use this skill to bypass CI checks?

No, the skill includes pre-push hooks and validation steps that block version tags if CI has failed or if the changelog is not properly updated.

Does this skill follow a specific changelog standard?

Yes, it follows the 'Keep a Changelog' conventions, organizing updates into Highlights, Changes, and Fixes sections within your CHANGELOG.md file.

How do I trigger a new release with this skill?

You can trigger a release by using the command '/release' followed by a version number or the keyword 'patch' (e.g., '/release 1.2.0' or '/release patch').

What happens after the release is pushed to GitHub?

The skill initiates a background process to watch the GitHub Actions publish workflow and will notify you of the final exit status of the CI run.

Is manual intervention required for the release process?

The skill automates most steps, but it will ask for explicit user confirmation before pushing tags to the remote repository to ensure final oversight.

Automated Release Manager

Name: Automated Release Manager
Author: tobi

bytobi

•

15,471

•

Despliegue y DevOps

Automates project versioning, changelog generation, and deployment workflows following standardized release conventions.

The Release skill provides a comprehensive framework for managing the software lifecycle within the qmd repository. It streamlines the complex process of cutting a new release by automating context gathering, validating changelog entries against 'Keep a Changelog' standards, and managing git hooks. By integrating version bumping, tag creation, and real-time GitHub Actions CI monitoring, this skill ensures that every release is consistent, well-documented, and safely deployed without the risk of manual errors or force-pushes.