kortix-release

Enforce semver versioning and main-to-prod deployment workflows for Kortix releases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill kortix-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kortix-release
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.claude/skills/kortix-release
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill kortix-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about kortix-release

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

FAQPage Schema
How do I generate accurate changelogs from git logs for production deployment?

To generate accurate changelogs for production deployment, you derive release notes directly from the full git log since the last release, ensuring public changelog entries exactly match the shipped code.

What is the correct git workflow for cutting a reliable production release?

The correct git workflow for a reliable production release follows a standardized main → promote → prod flow, enforcing strict semver rules and verifying deployment success to eliminate manual errors.

How do I roll back a broken production deployment without force-pushing?

You roll back a broken production deployment safely without force-pushing to protected branches by executing built-in zero-rebuild rollback procedures designed for live production incidents.

When should I use a patch, minor, or major version bump during release management?

You select a patch, minor, or major version bump during release management by applying strict semver guidance rules, eliminating guesswork to keep production release versioning consistent.

How do I safely undo a premature release cut before it reaches production?

To safely undo a premature release cut before it reaches production, you apply built-in production guardrails and recovery procedures that reverse unreleased cuts without risking branch integrity.

Does the Kortix release process require immutable version tags for production deployments?

Yes, the Kortix release process requires immutable version tags for production deployments to satisfy strict release guardrails and maintain protected production branch integrity.