release

Automate version bumps, manifests, and operator update instructions across a repository.

9|3|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/corca-ai/charness --skill release-corca-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/release
Command: npx skills add https://github.com/corca-ai/charness --skill release-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Maintainer tasks to cut, bump, and verify release surfaces across a repo are error-prone and inconsistent; this skill enforces a repeatable, auditable workflow.

Core Features & Use Cases

  • bootstrap and validate a release adapter setup
  • display current release state, drift, and checkpoints
  • perform bump, publish, and closeout steps with checks for premortem and real-host proof

Quick Start

Ask the agent to run the release workflow to bump or verify a repo's release surface.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps and manifest updates across a repository?

You can automate version bumps and manifest updates by running a release workflow driven by a deterministic release adapter. This enforces consistent release boundaries, validation, and publishing workflows across checked-in install metadata.

What is release drift detection and how does it work for package publishing?

Release drift detection identifies inconsistencies between your repository's current release state and expected checkpoints. It runs scripted checks during the workflow to ensure version bumps and manifests remain synchronized before publishing.

How do I validate a release adapter setup before cutting a new package version?

You validate a release adapter setup by bootstrapping the release workflow and running its scripted checks. This verifies packaging manifests, enforces release boundaries, and confirms all operator update instructions are correct before proceeding.

What are premortem and real-host proof gates in a release workflow?

Premortem and real-host proof gates are validation checks applied during bump, publish, and closeout steps. They anticipate potential release failures and verify the package surface works correctly on actual host environments.

Can I use this release workflow for plugin or package surfaces with checked-in install metadata?

Yes, this workflow specifically applies to plugin or package surfaces that ship checked-in install metadata. It automates maintainer-facing tasks to manage version bumps, manifests, and operator update instructions deterministically.

Why do manual maintainer release tasks cause inconsistencies across a repo?

Manual maintainer tasks to cut, bump, and verify release surfaces are error-prone because they lack repeatable, auditable workflows. Automating these tasks with a release adapter enforces consistent boundaries and validation checks.