kova-release-maintainer

Guide Kova release operations with guardrails, changelog generation, and validation sequencing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chiragborse1/KovaLab --skill kova-release-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kova-release-maintainer
Source: https://github.com/chiragborse1/KovaLab/tree/main/.agents/skills/kova-release-maintainer
Command: npx skills add https://github.com/chiragborse1/KovaLab --skill kova-release-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates risky, inconsistent release operations by guiding maintainers through a guarded, end-to-end workflow for preparing and publishing Kova stable or beta releases with correct versions, changelogs, and validation.

Core Features & Use Cases

  • Release guardrails & decision rules: Enforces safe handling of version changes, npm publish permission, stable vs beta defaults, branch-cut strategy, and tag naming alignment.
  • Changelog-backed release notes: Rewrites the target CHANGELOG.md section from commit history and extracts the exact version block for GitHub release bodies (with upcoming deprecations callouts).
  • Compatibility and deprecation safety checks: Reviews compatibility registry and doctor deprecation records to prevent shipping expired removal-pending paths without explicit approval.
  • Production-grade validation sequencing: Defines the correct preflight and roster of checks (npm preflight, install smoke, Docker/Parallels verification, release-check, and post-publish validation) while avoiding tag rewrite pitfalls.
  • Release comms templates: Provides consistent release tweet and announcement guidance, including beta vs stable tone and linking to the right release artifacts.

Quick Start

Ask the skill to prepare a beta release for version 2026.4.20 from the correct release/YYYY.M.D branch, using /changelog notes and the required validation sequence before any publish step.

Frequently Asked Questions about kova-release-maintainer

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

FAQPage Schema
How do I generate changelog release notes from commit history for npm publish?

To generate changelog release notes from commit history for npm publish, the Skill rewrites the target CHANGELOG.md section from commits and extracts the exact version block for GitHub release bodies, including upcoming deprecation callouts.

What is the correct validation sequence for a beta release branch cut?

The correct validation sequence for a beta release branch cut involves running npm preflight, install smoke tests, Docker/Parallels verification, release-check, and post-publish validation to ensure deterministic sequencing and avoid tag rewrite pitfalls.

How do I check compatibility and deprecation safety before shipping a release?

To check compatibility and deprecation safety before shipping, the Skill reviews the compatibility registry and doctor deprecation records to prevent shipping expired removal-pending paths without explicit maintainer approval.

Does this release workflow enforce non-rewrite tag policies for GitHub releases?

Yes, the release workflow enforces non-rewrite tag policies for GitHub releases by applying decision rules for tag naming alignment, stable versus beta defaults, and safe branch-cut strategy to eliminate risky operations.

Can I use this to prepare stable and beta release comms templates?

Yes, you can use this to prepare stable and beta release comms templates, which provide consistent release tweet and announcement guidance with the correct beta versus stable tone and links to the right release artifacts.

Why does CI green check validation fail before npm publish?

CI green check validation fails before npm publish when preflight checks, install smoke tests, or compatibility and deprecation reviews detect expired removal-pending paths or misaligned tag naming, blocking the release until explicit approval is granted.