Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tractorjuice/release
Cut a new ArcKit release — bump versions in lockstep, regenerate non-Claude formats, validate plugin/marketplace agreement, tag, and push to standalone repos.
Passed 11 of 18 test cases with the skill, and 7 of 18 without it.
and 5 more in the full report
8 fixed6 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want push-extensions.sh to synchronize standalone repository code without creating release tags or GitHub releases. What environment variable enables this?
| Checked | Without skill | With skill |
|---|---|---|
| Sets ARCKIT_SKIP_EXTENSION_RELEASES=1. | Missed | Passed |
The instructions your model reads when the skill loads.
Drive the ArcKit release flow end to end. This skill is the executable companion to
docs/RELEASING.md — that doc is the source of truth; if the two
disagree, trust RELEASING.md and update this skill.
The target version is $ARGUMENTS (e.g. /release 5.10.0). If no version was given, ask
for it before doing anything — never guess a version.
Confirm all of these before touching version files:
main — releases are cut from main, never from a branch.main and clean: git checkout main && git pull && git status.$ARGUMENTS is valid semver (X.Y.Z) and greater than the current
plugin version (cat plugins/arckit-claude/VERSION) and CLI version (cat VERSION).GH_TOKEN is set in the environment (needed by push-extensions.sh).If any precondition fails, stop and surface it. Do not work around it.
Run these in order. Each script is idempotent or safe to re-run except the git tag/git push
steps. Pause after step 6 (the commit) and after step 8 before tagging to let the user confirm.
# 1. Edit CHANGELOGs by hand — both of them:
# CHANGELOG.md (CLI) and plugins/arckit-claude/CHANGELOG.md (plugin).
# Preview what shipped since the last tag to seed the entries:
./scripts/generate-release-notes.sh
# 2. Bump every version file in lockstep (15 locations: VERSION files,
# manifests, README badges, docs, plugin.json):
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.