hatch3r-release

Automates release prep: versioning, changelogs, tagging, publishing, and verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you consistently prepare and ship a software release without missing critical steps like versioning, changelogs, quality gates, tagging, and post-deploy verification.

Core Features & Use Cases

  • Version bump selection: Decide major/minor/patch based on merged changes and Semantic Versioning guidance.
  • Changelog generation: Produce grouped release notes (including breaking changes when applicable) from PR/MR history.
  • Release execution with verification: Update package versions and lockfiles, run lint/typecheck/tests/build, create/push tags, publish a platform release, then deploy and monitor for regressions.
  • Pre-release and rollback support: Handle alpha/beta/rc distribution tags and provide safe rollback/deprecation procedures when quality gates fail or post-deploy errors spike.

Quick Start

Run the hatch3r-release skill to bump your version, generate the changelog, tag and publish the release, then deploy to staging or production and verify outcomes.

Frequently Asked Questions about hatch3r-release

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

FAQPage Schema
How do I automate version bump selection and changelog generation for a production release?

Automate version bump selection and changelog generation by evaluating merged PR/MR history against Semantic Versioning rules, then grouping changes into categorized release notes including breaking changes. This ensures consistent versioning and documented release preparation without manual intervention.

What's the best way to create pre-releases like alpha, beta, or rc with proper quality gates?

Create pre-releases by applying alpha, beta, or rc distribution tags after executing pre-release quality gates. The process evaluates CI quality gates and project checks before tagging, ensuring only validated code progresses to pre-release distribution.

How does deploy verification and rollback work when post-deploy errors spike after a new release?

Deploy verification monitors post-deploy outcomes for regressions or error spikes, triggering rollback and deprecation procedures when failures occur. This automated monitoring catches deployment issues immediately after platform-aware tag and release creation.

Can I use CI quality gates to validate changes before pushing git tags and publishing a release?

Yes, CI quality gates validate changes by running lint, typecheck, tests, and build checks before creating and pushing git tags. Platform-aware tag and release creation only proceeds after all quality gates pass successfully.

What is Semantic Versioning guidance for deciding major, minor, or patch version bumps?

Semantic Versioning guidance determines major, minor, or patch bumps by analyzing merged changes from platform PR/MR history. Breaking changes trigger major bumps, new features trigger minor bumps, and fixes trigger patch bumps for accurate release versioning.

Why does release preparation fail when package versions and lockfiles are not updated together?

Release preparation fails when package versions and lockfiles are inconsistent because quality gates like lint, typecheck, tests, and builds depend on synchronized dependencies. Updating both ensures CI checks pass before git tagging and publishing.