Menu
Cut a new gcrunner release — bumps version in all files, commits, tags, and pushes. Usage: /release v0.2.0
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CamdenClark/gcrunner --skill releaseThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | release |
| description | Cut a new gcrunner release — bumps version in all files, commits, tags, and pushes. Usage: /release v0.2.0 |
Release version: $ARGUMENTS
First, confirm the version looks like a valid semver tag (e.g. v0.2.0). If not, stop and tell the user.
Read terraform/variables.tf and note the current gcrunner_version default so you can show what's changing.
Update the version string from the old value to $ARGUMENTS in:
terraform/variables.tf — the default value of gcrunner_versionREADME.md — two occurrences:
cloudshell_git_branch=<old> in the Cloud Shell badge URLgit clone --branch <old> in the deploy commandtutorial.md — TF_VAR_gcrunner_version=<old> in the configure variables stepwebsite/content/docs/updating.md — git clone --branch <old> in the manual update stepStage and commit only those four files:
git add terraform/variables.tf README.md tutorial.md website/content/docs/updating.md
git commit -m "Bump version to $ARGUMENTS"
git tag -a $ARGUMENTS -m "Release $ARGUMENTS"
Show the user what you're about to push (commit + tag) and ask them to confirm before running:
git push origin HEAD
git push origin $ARGUMENTS