release

Solid

Cut a new kimiflow release — promote CHANGELOG, bump manifests, regenerate the canonical runtime candidate, run all gates, commit, tag, push, and delegate immutable GitHub publication to the tracked publisher. Fully automatic but fail-closed. Local maintainer tool for the kimiflow repo.

AI & Automation 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /release — kimiflow release Fully automatic release of the kimiflow plugin, from version bump through the published GitHub release. ## Mode & safety (read first) - **Fully automatic:** no approval stops in the happy path. This skill **pushes to `origin/main` and publishes a public GitHub release without asking** — that is the configured behaviour. - **Fail-closed:** every gate below **aborts** (it does *not* prompt) when a precondition fails. A broken/duplicate release is worse than no release. On any abort: stop, show the failing command + the decisive output line(s), change nothing further. - **Reply in the user's language. Terse output:** one line per step + the decisive evidence. Never paste full logs. - **Source of truth for "which files must carry the version":** `hooks/release-consistency-check.sh`. If that script and this skill ever disagree, the script wins — re-read it. ## 0. Preconditions — hard gates (abort on any) 1. **Repo root:** `.claude-plugin/plugin.json` exists in the cwd. Else abort ("run from the kimiflow repo root"). 2. **Tools:** `jq` and `gh` are on PATH. Else abort. 3. **Branch:** `git rev-parse --abbrev-ref HEAD` is `main`. Else abort. 4. **Clean tree:** `git status --porcelain` is empty. (`.kimiflow/`, `.claude/worktrees/`, and `.claude/skills/` are gitignored and won't appear.) If dirty → abort: "commit or stash first". 5. **In sync with origin:** `git fetch origin`, then verify local `main` is **not behind** `origin/main` (`git rev-list --l...

Details

Author
kimikonapps
Repository
kimikonapps/kimiflow
Created
1 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

release

Cut an ibkr release end-to-end with exactly one human stop. Autonomously preflights auth (verify-first Actions-OIDC), shared-tree state, version stamps, changelog, and gates; presents a findings-first GO/NO-GO; then fires and supervises `make release` and runs the full post-release verification (assets, tags, registry, fresh-clone build, live site stamps). Use when asked to cut, ship, prepare, or verify a release. Never tags, pushes, or creates GitHub releases directly; never force-pushes; never implements feature code in-release.

5 Updated yesterday
osauer
AI & Automation Listed

release

Run a versioned release with git-flow discipline: deterministic preflight (branch, clean tree, Conventional Commits since last tag → suggested semver bump), changelog entry written from fragments/commits into the changelog file automatically, then the exact squash-merge/tag/push/GitHub-release sequence printed and consent-gated by default (configurable auto mode). Two configurable modes: light (dev → main) and full git-flow (release/* stabilization + hotfix/* branches). Use for 'release', 'cut a release', 'ship a version', 'bump the version', 'publish vX.Y.Z', 'hotfix production' — whenever accumulated work should become a tagged, published version.

1 Updated 3 days ago
supermodo
AI & Automation Solid

release

Cut a new ArcKit release — bump versions in lockstep, regenerate non-Claude formats, validate plugin/marketplace agreement, tag, and push to standalone repos. Use when the user says 'cut a release', 'release ArcKit', 'ship vX.Y.Z', 'bump the version and release', 'do the release flow', 'tag and publish', or 'push the extensions'. This is a manual, high-consequence workflow: it never runs automatically.

2,103 Updated today
tractorjuice