Release Management

Automate semantic versioning, changelog generation, and git tagging for releases.

1|Updated May 28, 2025
One-click install
npx skills add https://github.com/hackur/web-standards-playground-showcase --skill release-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release Management
Source: https://github.com/hackur/web-standards-playground-showcase/tree/main/.claude-laravel-backup/skills/release-management
Command: npx skills add https://github.com/hackur/web-standards-playground-showcase --skill release-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates release workflows including version bumps, changelogs, and git tagging.

Core Features & Use Cases

  • Semantic versioning with patch/minor/major releases
  • Changelog generation from commits
  • Git tagging and publishing releases for production deployment readiness

Quick Start

Run a full release: DRY_RUN=false ./scripts/release.sh full patch

Frequently Asked Questions about Release Management

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

FAQPage Schema
How do I automate semantic versioning and changelog generation for my project?

Semantic versioning automates version bumps (patch, minor, major) and generates changelogs from conventional commits. This Skill handles the full workflow: analyzing commits, updating version fields in package.json and composer.json, creating git tags, and generating CHANGELOG.md entries in a four-step process.

Can I use this release automation with my CI/CD pipeline?

Yes. This Skill integrates with CI/CD pipelines, supporting dry-run safety, pre-flight validation, interactive confirmations, and rollback procedures. Run releases via scripts that execute the four-step workflow (Current, Prepare, Tag, Publish) for production deployment readiness.

What's the best way to manage git tagging and versioning with conventional commits?

Conventional commits enable automatic release workflows. This Skill parses commits, determines version bumps (patch, minor, major), generates tags, and updates CHANGELOG.md automatically. Use the full release workflow or individual steps for fine-grained control.

Do I need to manually create git tags and update changelogs for each release?

No. This Skill automates both tasks. It generates git tags based on semantic versioning rules, creates CHANGELOG.md entries from commits, and bumps versions across package.json and composer.json files in a single workflow.

How does dry-run mode help with release workflows?

Dry-run mode previews all changes—version bumps, changelog entries, and git tags—without applying them. This validates your release before execution. Set DRY_RUN=false to apply changes when ready.

What happens if a release goes wrong—can I roll back?

Yes. This Skill includes rollback procedures to undo releases. Combined with dry-run validation and interactive confirmations, you can safely test and recover from release errors.