release

Automate release management with changelog validation, version bumps, and git tagging.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill release-jaimejunr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/release
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill release-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Release management ensures changelog accuracy, proper versioning, and enforced hooks before pushing releases.

Core Features & Use Cases

  • Validate and package new releases by gathering context, updating CHANGELOG, and bumping version numbers.
  • Install and maintain pre-push git hooks to enforce release standards and guard against skipped steps.
  • Automate pushing, tagging, and CI monitoring to ensure releases flow smoothly from local development to CI.

Quick Start

Run the release flow with a target version, e.g., '/release 1.0.5' to cut a new release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git release management with changelog validation and version bumps?

Git release management is automated by gathering context, validating the CHANGELOG, and bumping version numbers before tagging. The release flow enforces these standards using pre-push git hooks to guard against skipped steps.

What's the best way to enforce pre-push hooks for versioning and changelog updates?

Pre-push hooks enforce versioning and changelog updates by installing git hooks that gate releases before pushing. This ensures validated changes are tagged locally and in CI workflows before any code is pushed.

How do I cut a new release version and tag it in a CI workflow?

To cut a new release version, run the release flow with a target version number like '1.0.5'. The process prepares context, bumps versions, tags the release, and monitors CI workflows to ensure smooth delivery.

Can I use this release automation locally and in CI environments?

Yes, release automation applies across both local development and CI workflows. It coordinates the end-to-end release process by validating changes, enforcing pre-push hooks, and monitoring publish watch workflows.

Why do I need pre-push gating before pushing a new release tag?

Pre-push gating is needed to enforce release standards and prevent skipped steps like missing changelog entries or invalid version bumps. It ensures all required validations pass before pushing tags to the repository.

How does the release process extract and validate changelog entries?

The release process extracts and validates changelog entries using dedicated scripts that gather context and verify changes. This ensures changelog accuracy and proper versioning before tagging the release.