Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zenml-io/kitaru-release
Guide the Kitaru release process end-to-end — diff develop against the last tag, classify commits (src / docs content / docs infra / release infra), filter docs-infra-only PRs out of the Python library CHANGELOG, remember that marketing-site work now lives in sibling zenml-io-v2, check zenml-io/zenml-frontend-monorepo for the latest stable kitaru-ui-v* release that will be bundled into the Python package and then copied into the Docker image, suggest a version bump, update CHANGELOG.md, run the
Passed 20 of 23 test cases with the skill, and 8 of 23 without it.
and 14 more in the full report
14 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When core version `1.5.0` is ready to be published after PR merge, what exact git tag string must be created on the commit to trigger the publication workflow?
| Checked | Without skill | With skill |
|---|---|---|
| Uses git tag format python/kitaru/v1.5.0. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the current workflows as the source of truth:
.github/workflows/release.yml.github/workflows/release-plugins.ymlrelease/release-units.tomlzenml-io/zenml-frontend-monorepo/.github/workflows/release-kitaru-ui.ymlRead AGENTS.md. Read plugins/AGENTS.md and plugins/DEVELOPMENT.md for plugin changes. Read FRONTEND-TESTING.md for core or UI work.
Do not create a tag, dispatch a publishing workflow, approve an environment, or publish an artifact without explicit user confirmation. A request to prepare a release authorizes a release PR only.
Ask only for choices that cannot be derived from the repository and registries.
kitaru, the selected UI, public images, the managed image, and Helm from one core tag.There is no separate bundle tag. The core tag publishes the Python package and deployables in one workflow.
Confirm the selected distributions, versions, frontend tag, publication order, and release commit before editing.
X.Y.Z or X.Y.ZrcN.X.Y.ZrcN to X.Y.Z-rc.N for Docker and Helm.vX.Y.Z or vX.Y.Z-rc.N as the frontend workflow input.kitaru-ui-vX.Y.Z or kitaru-ui-vX.Y.Z-rc.N.X.Y.Z.Perform this section before the core preparation PR when the core needs a new UI release.
zenml-io/zenml-frontend-monorepo and select an exact commit on main.test cases passed, vs 8 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.