skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:deploy-release

Automate Git release creation with semantic versioning and changelog updates.

Updated Mar 26, 2026
Search Tags:#git#conventional commits#semantic versioning#release automation#tagging#github releases#changelog generation
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-deploy-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:deploy-release
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/deploy-release
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-deploy-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of manually creating Git releases by automating version selection, changelog generation, tagging, and (when applicable) GitHub release publishing.

Core Features & Use Cases

  • Creates a release-ready version: Accepts an explicit semantic version or computes one from commit history since the last tag.
  • Generates a changelog entry and release notes: Groups conventional commits and produces release notes prose for the GitHub release while updating CHANGELOG.md.
  • Publishes the release: Adds an annotated git tag, pushes it to the remote, and creates a GitHub release marked as latest.
  • Use Case: You need to cut a new release for a project after merges and want consistent semver bumps, a fresh CHANGELOG.md entry, and a GitHub release in a repeatable workflow.

Quick Start

Run wa:deploy-release with an explicit version like 1.3.0 to generate the changelog, create and push the tag, and publish the corresponding GitHub release.

Frequently Asked Questions about wa:deploy-release

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

FAQPage Schema
How do I automate semantic versioning and changelog generation from conventional commits?▼

Automate semantic versioning and changelog generation by deriving a version bump from conventional commit history, grouping commits into categorized entries, and appending them to CHANGELOG.md.

What is the best way to create a GitHub release from a git tag using conventional commit history?▼

Create a GitHub release from an annotated git tag by generating release notes from conventional commit history, pushing the tag to the remote, and publishing the release marked as latest.

Does release automation work if I provide an explicit semantic version instead of computing it from commits?▼

Release automation works with an explicit semantic version, bypassing commit history derivation and proceeding directly to changelog generation, tagging, and GitHub release publishing.

How do I handle git tag collisions or empty release ranges during release automation?▼

Handle git tag collisions and empty release ranges through built-in error handling that validates release ranges, detects tag conflicts, and halts publication failures before proceeding.

Can I use conventional commit grouping to generate release notes for a GitHub release?▼

Use conventional commit grouping to generate release notes by categorizing commit history since the last tag into structured prose for the GitHub release body and CHANGELOG.md entry.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

GitHub Tag

Automate creation, management and pushing of semantic Git tags.

Community
Intermediate
mir-ammir-am
1

gh-release

Create annotated git tags and publish GitHub prereleases from changelog versions.

Community
Intermediate
ntk148vntk148v
1

conventional-commits

Generate conventional commit messages with type, scope, and breaking change markers.

Community
Basic
DonTiziDonTizi
2

release

Automate Python project releases with version bumps, changelog updates, and Git tags.

Community
Advanced