Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sonichi/release
Prepare, verify, and publish Sutando engine releases.
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
and 4 more in the full report
7 fixed9 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
What exact decision status text must be written at the end of the release proposal document before owner review?
| Checked | Without skill | With skill |
|---|---|---|
| Requires exact line publish: pending owner confirmation. | Missed | Passed |
The instructions your model reads when the skill loads.
Use docs/release-process.md as policy. Do not
duplicate or reinterpret it here. This skill turns that policy into an
evidence-backed workflow.
Never infer publish permission from “prepare,” “get ready,” a green CI run, or an approved release PR.
Read docs/release-process.md completely.
Resolve the repository and workspace:
REPO="$(git rev-parse --show-toplevel)"
WORKSPACE="$(bash "$REPO/scripts/sutando-config.sh" workspace)"
Identify the last release tag and the exact candidate SHA. Compare the tag to the candidate; do not rely only on PR titles.
Classify the change set:
Run the documentation audit:
python3 skills/release/scripts/docs_audit.py
test cases passed, vs 7 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.