release

Automate Kukicha releases by bumping versions, regenerating stdlib, running tests, and pushing tags.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end Kukicha release process, ensuring version bumps, stdlib regeneration, test execution, and Git tagging/pushing are performed consistently and auditable across releases.

Core Features & Use Cases

  • End-to-end release workflow: bump version, regenerate artifacts, run tests, commit changes, tag, and push.
  • SemVer-aligned releases: enforces semantic versioning discipline and consistent release notes across docs.
  • Use Case: when preparing a new Kukicha release after features or fixes have landed and you need a repeatable, auditable process.

Quick Start

Run the release process to cut a new Kukicha version by bumping the version, regenerating stdlib, running tests, and pushing the tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and Git tagging for a release?

Automate version bumping and Git tagging by running an end-to-end release workflow that updates version files, regenerates stdlib, runs tests, and pushes tags.

How does semantic versioning enforcement work during a release?

Semantic versioning enforcement applies SemVer rules during the release process, ensuring consistent version bumps and standardized release notes across documentation.

What's the best way to regenerate stdlib before tagging a release?

Regenerating stdlib before tagging is handled automatically by the release workflow, which executes artifact regeneration and validates tests prior to committing and pushing Git tags.

Can I run release workflows across multiple branches and environments?

Release workflows support execution across multiple branches and environments, allowing developers and release engineers to apply consistent versioning, testing, and tagging operations.

Do I need to run tests before pushing a Git tag?

Running tests before pushing a Git tag is required, as the release workflow validates test suite execution and updates documentation before committing changes and tagging.

Why does the release process update internal version files?

Updating internal version files ensures the codebase reflects the new SemVer version, maintaining consistency between source code, regenerated artifacts, and Git tags across releases.