Determine semantic versions, create Git tags, and push to trigger CI releases.
npx skills add https://github.com/asklar/lvt --skill release-asklar
Please help me install this Agent Skill. Skill: release Source: https://github.com/asklar/lvt/tree/main/.github/skills/release Command: npx skills add https://github.com/asklar/lvt --skill release-asklar
Release management for software projects is often manual and error-prone. This Skill automates versioning, tagging, and publishing to the release pipeline, reducing manual steps and ensuring reproducible releases.
Ask me to release a new version with a bump type (patch, minor, or major) and I will perform the version update, tagging, and push to trigger the release pipeline.
High-intent search queries and answers about installing and using this skill.
Automating semantic versioning involves determining the next version bump, creating an annotated Git tag like vX.Y.Z, and pushing it to the remote to trigger CI pipelines. This process reduces manual errors and ensures reproducible software deployments.
Generating release notes from Git commits involves reading the commit history since the last tag and compiling the changes into a changelog. This is often integrated into the release workflow to provide auditable documentation for each new version.
Yes, enforcing a clean working directory and validating that you are on the main branch before creating a version tag ensures release integrity. This prevents uncommitted changes from being included in an auditable and reproducible deployment.
Pushing an annotated Git tag to the remote triggers CI-CD release workflows by signaling the version control system to execute the publishing pipeline. This mechanism guarantees that deployments are tied to specific, reproducible version states.
Yes, you can use this for patch, minor, or major version releases by specifying the bump type. The system determines the next semantic version based on your input and the project history, then applies the corresponding tag to trigger the pipeline.
Automated releases fail branch checks when you are not on the main branch or have uncommitted changes in your working tree. The release process enforces these validations to maintain release integrity and prevent deploying unverified code.
TMI-appsValidate and push committed Git changes to a remote repository.
richardrimanAutomate GitHub releases with notes and binary uploads via gh CLI.
kirvinAutomate versioned software releases with semantic versioning and GitHub CLI.
gaebalaiPlan release tagging and CHANGELOG strategy using semantic versioning.
