release

Automate the Context CLI release workflow with version and release-note checks.

74|14|Updated Jan 20, 2026

Search Tags:#automation #git #versioning #release #docs #ci-cd

Ready to run

npx skills add https://github.com/ActiveMemory/ctx --skill release-activememory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ActiveMemory/ctx/tree/main/.claude/skills/release
Command: npx skills add https://github.com/ActiveMemory/ctx --skill release-activememory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing the Context CLI involves multiple coordinated steps, and manual handling risks version drift, missing release notes, and inconsistent documentation. This skill automates the end-to-end release process to ensure all prerequisites are met and artifacts are published reliably.

Core Features & Use Cases

Verifies prerequisites (VERSION updated, dist/RELEASE_NOTES.md present, clean working tree) and aborts if any check fails.
Orchestrates the release pipeline: updates docs, builds binaries, creates and signs git tags, and pushes release artifacts.
Use Case: Cut a new ctx version after QA approval to ship to users with accurate release notes and updated docs.

Quick Start

Trigger the full ctx release workflow to publish a new version.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate the CLI release process end-to-end?▼

Automating the CLI release process requires validating prerequisites like VERSION updates and release notes, then orchestrating build pipelines, signing git tags, and pushing artifacts. This ensures version alignment and reliable documentation updates.

What prerequisites are required before cutting a new ctx version?▼

Before cutting a new ctx version, you need an updated VERSION file, present dist/RELEASE_NOTES.md, and a clean working tree. The automated workflow verifies these prerequisites and aborts the release if any check fails.

Why does my automated release workflow abort before tagging?▼

Your automated release workflow aborts when prerequisite checks fail, specifically if the VERSION file is outdated, dist/RELEASE_NOTES.md is missing, or the git working tree is not clean before attempting to sign tags.

How does git tagging work in an automated versioning pipeline?▼

In an automated versioning pipeline, git tagging occurs after validating prerequisites and running build pipelines. The workflow creates and signs git tags to mark the release commit before pushing artifacts and updating documentation.

What's the best way to ensure version alignment and release-note integrity during a CLI release?▼

The best way to ensure version alignment and release-note integrity is automating the end-to-end release workflow, which validates the VERSION file and RELEASE_NOTES.md, orchestrates builds, and pushes signed git tags.