release

Coordinate branch creation, version bumps, changelog generation, PR flow, and GitHub Release tagging.

27|2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/edochi/mdvs --skill release-edochi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/edochi/mdvs/tree/main/.claude/skills/release
Command: npx skills add https://github.com/edochi/mdvs --skill release-edochi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mdvs releases are coordinated through a branch + PR workflow, with version bumps, changelog generation, and GitHub Release tagging to ensure releases are reproducible and auditable.

Core Features & Use Cases

  • Branch-based release workflow: create a dedicated release branch from main, validate changes, and prepare for release.
  • Version bumps & changelog: automatically update the version and generate a changelog from conventional commits.
  • PRs, tags, and GitHub Release: open a release PR, create a git tag, and publish release notes to GitHub.

Quick Start

Initiate a release by creating a release branch, bumping the version, pushing, opening a PR, and tagging the release.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a git release workflow with version bumping and changelog generation?

Automate a git release workflow by coordinating branch creation, version bumping, and changelog generation from conventional commits. This ensures tests pass and the main branch is clean before opening a PR and tagging a GitHub Release.

What is a branch-based release workflow for versioning and GitHub releases?

A branch-based release workflow creates a dedicated release branch from main to validate changes, bump versions, and generate changelogs. It ensures reproducible, auditable releases by requiring passing tests and green CI before tagging.

Can I create release candidates and major version bumps using an automated release workflow?

Yes, automated release workflows support patch, minor, major, and release-candidate releases. The process coordinates branch creation, version bumping, PR flow, and GitHub Release tagging for each release type.

How do I ensure CI is green and tests pass before tagging a GitHub release?

Ensure CI is green and tests pass before tagging by applying release guardrails specified within the workflow. These guardrails require a clean main branch, passing tests, and green CI status before a release tag is created.

How do I generate a changelog from conventional commits for a release PR?

Generate a changelog from conventional commits automatically as part of the release workflow. When creating a release branch, the workflow updates the version and compiles commit messages into a structured changelog for the PR.

What are the prerequisites for running an automated release workflow with git and GitHub?

Prerequisites for running an automated release workflow include a clean main branch, passing tests, and green CI. The workflow specifies these guardrails within its configuration to enable reproducible, auditable releases.