release-engineering

Automate version bumps, changelog updates, and tag verification across repositories.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill release-engineering-jce-joshhh77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-engineering
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/release-engineering
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill release-engineering-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version control and release workflow discipline, including version bumps, changelog updates, and tag/commit hygiene, to ensure predictable shipping.

Core Features & Use Cases

  • Version synchronization across metadata, installers, constants, tests, and generated references
  • Changelog generation, release notes preparation, and verification gates
  • Verified push/tag workflows with pre-release checks, review steps, and rollback considerations
  • Use Case: When preparing a multi-package release, align all artifacts, update documentation, and ensure CI checks pass before tagging.

Quick Start

Execute a release increment, verify changes across packages, and push with tags following the project's release policy.

Frequently Asked Questions about release-engineering

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

FAQPage Schema
How do I automate version bumps and changelog updates for a multi-package release?

Version synchronization across multi-package repos involves aligning metadata, installers, constants, and tests before tagging. This workflow automates version bumps, updates changelogs, and enforces commit hygiene to ensure predictable shipping across all project artifacts.

What is the best way to manage git tag verification and pre-release checks?

Git tag verification and pre-release checks require applying verified push workflows with rollback considerations. This process ensures CI checks pass and includes optional review steps before safely executing push and tag operations during deployment.

How do I prepare release notes and verify changes across packages before deployment?

Preparing release notes and verifying changes across packages involves generating changelogs and applying verification gates. This ensures all generated references, documentation, and artifacts are aligned and validated before initiating the final deployment process.

Does this release management workflow support monorepos with standard CI checks?

Yes, this release management workflow applies to software projects with standard release processes, including multi-package repos and CI checks. It handles version synchronization and artifact publishing within monorepo configurations effectively.

Why do I need commit hygiene and versioning discipline in my deployment process?

Commit hygiene and versioning discipline are needed to ensure predictable shipping and prevent deployment failures. They enforce version synchronization across metadata and tests, maintaining release workflow integrity throughout the software lifecycle.