kortix-release

What problem does it solve?

Manually cutting Kortix production releases leads to versioning errors, inconsistent public changelogs, accidental unvetted changes to the production environment, and broken deployments if strict release guardrails are not followed.

Core Features & Use Cases

• Strict Semver Guidance: Clear, actionable rules for when to use patch, minor, or major version bumps to eliminate guesswork and keep release versioning consistent.
• End-to-End Release Workflow: Step-by-step process to derive 100% accurate release notes from the full git log since the last release, run the Promote workflow, and verify successful production deployment.
• Production Guardrails & Recovery: Built-in procedures to safely undo premature unreleased cuts and roll back live broken releases without force-pushing to protected production branches. Use case example: Engineering teams shipping Kortix updates can use this skill to ensure every release follows the required main → promote → prod flow, generates changelog entries that exactly match shipped code, and recovers quickly from bad releases without risking production integrity.

Quick Start

Use the kortix-release skill to cut a new production release for the latest changes merged to the Kortix main branch.