release

Prepares version bumps, changelogs, and rollout plans for approved releases.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/kreek/consult --skill release-kreek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kreek/consult/tree/main/plugin/skills/release
Command: npx skills add https://github.com/kreek/consult --skill release-kreek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Release work involves coordinating version bumps, changelogs, lockfiles, tags, and rollback plans across many artifacts, and mistakes can break users or shared environments. This Skill structures release preparation so agents produce evidence and plans while humans retain control of anything that mutates shared environments. ## Core Features & Use Cases - Release Unit Classification: Maps release units from manifests, lockfiles, workspace config, and tags, then classifies impact to choose the correct semver bump per unit, including monorepos with independent streams. - Artifact Synchronization: Keeps manifests, committed lockfiles, CHANGELOG entries, tag plans, dependency ranges, and publish order moving together, with validation via dependency resolution and dry-run packaging. - Rollout and Rollback Planning: Prepares rollout plans with named artifacts, environments, operators, and gates, plus rollback covering data, caches, config, and external side effects. - Deprecation and Migration Guidance: Loads a dedicated reference for advisory deprecations, compulsory migrations, removals, and internal cleanups with proof obligations. - Use Case: After a breaking API change is approved, use this Skill to determine the major version bump, update the changelog and lockfile together, and draft a rollback runbook for a human operator to execute. ## Quick Start Ask the agent to prepare the release for the approved changes, including version classification, changelog updates, and a rollback plan.

Frequently Asked Questions about release

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

FAQPage Schema
How do I prepare a release with version bump and changelog?▼

Confirm the release gate and scope, map release units from manifests and lockfiles, classify impact to pick the target version, then edit artifacts together and validate. Breaking changes always bump the major version.

How should versioning work in a monorepo with multiple packages?▼

Classify each release unit separately, since libraries, CLIs, plugin manifests, and containers may have independent streams. Lockstep bumps require repo policy or explicit user approval, and unclear compatibility uses the higher plausible bump.

Can the agent run deployments or rollbacks directly?▼

No. Agents prepare evidence, checklists, runbooks, and command plans, while humans execute anything that mutates shared environments, including staging config and feature flags. Agent-run checks and human-run commands are reported separately.

What makes a good rollback plan for a release?▼

Rollback must be faster than fix-forward and cover data, caches, config, and external side effects, not just code. Keep canary or progressive gates in place, or name the equivalent safeguard.

When should a feature flag default to on?▼

Feature flags default off and carry an owner, expiry, cleanup work, and a human-owned production change path. The only exception is a kill-switch guarding existing behavior.

When should this release skill not be used?▼

Do not start release work just because a change might later need it; note the risk and wait for a concrete release-prep decision point. Database DDL safety belongs to the database skill, and local bootstrap belongs to scaffolding.