release
SolidCut 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.
Install
Quality Score: 78/100
Skill Content
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
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.
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.
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.