skills.rest
marcel-heinz
marcel-heinzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Coordinate ClawCity release workflows with version bumps, changelog updates, git tagging, and GitHub releases.

4|2|Updated Jan 30, 2026
Search Tags:#changelog#deployment#github#release#semver#tagging
One-click install
npx skills add https://github.com/marcel-heinz/clawcity.app --skill release-marcel-heinz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/marcel-heinz/clawcity.app/tree/main/.claude/skills/release
Command: npx skills add https://github.com/marcel-heinz/clawcity.app --skill release-marcel-heinz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare and publish a new ClawCity release. The process ensures version bumps, changelog updates, git tagging, and GitHub release publication.

Core Features & Use Cases

  • End-to-end release orchestration: bumps version, updates changelog, tags the release, and creates a GitHub release.
  • Semantic versioning discipline: aligns changes with vX.Y.Z conventions and optional CLI publish.
  • Release verification: validates that the release is live and links are correct.

Quick Start

Trigger the release agent to prepare and publish a new ClawCity version, including changelog updates, git tagging, and GitHub release notes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a GitHub release workflow with changelog updates and semantic versioning?▼

You can automate a GitHub release workflow by bumping the semantic version, updating the changelog, creating a git tag, and publishing the release. This ensures consistent vX.Y.Z tagging and accurate release notes.

What is the best way to manage semantic versioning and git tagging for CLI deployments?▼

Managing semantic versioning for CLI deployments involves aligning code changes with vX.Y.Z conventions, creating git tags, and optionally publishing the updated CLI package to verify the release is live.

How does changelog generation work during an end-to-end release process?▼

Changelog generation during a release process aggregates committed changes, updates the CHANGELOG file automatically, and pairs the entries with the corresponding semantic version git tag before publishing the GitHub release.

Can I verify a GitHub release is live and links are correct after publishing?▼

Yes, release verification validates that the GitHub release is live and confirms that all associated links are correct, ensuring the published version and its assets are accessible immediately after deployment.

Do I need a separate deployment tool to publish a CLI package after creating a git tag?▼

No, an end-to-end release orchestration process can optionally publish the updated CLI package directly after handling the version bump and git tagging, streamlining the deployment without needing separate tools.

Related Skills

Explore More Product & Management Skills→
haleyrchaleyrc
2

stele-release

Automate semantic version bumping and release preparation for the stele CLI project.

Community
Advanced
oogDZoogDZ

post-release

Validate GitHub Release notes, CHANGELOG updates, and deployment statuses after publication.

Community
Intermediate
levkisslevkiss

github

Manage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.

Community
Advanced
HouseofmvpsHouseofmvps
115

release

Automate changelog generation, version bumping, git tagging, GitHub releases, and npm publishing for Node.js projects.

Community
Intermediate