loope: Skill for Claude Code

Cutting a loope release

Announce at start: "Using release-new-version to cut a release."

This procedure is stop and report, never unwind. If any step fails, say which step failed and what has already happened, then stop. Never run git reset, git tag -d, git push --force, gh release delete, git stash, git checkout, or git pull in this skill — not even to clean up after yourself. A half-finished run is safe to re-run.

Never propose a version number. The author types it.

Step 1 — Preflight

Run in one Bash call:

echo "branch: $(git rev-parse --abbrev-ref HEAD)"
echo "dirty: [$(git status --porcelain)]"
git fetch --tags origin
echo "divergence: $(git rev-list --left-right --count origin/main...HEAD)"
gh auth status

Stop if any of these hold, reporting exactly which check failed:

Do not stash, reset, checkout, or pull on the author's behalf. Tell them what to fix and stop.

Step 2 — Establish the range

git describe --tags --abbrev=0

• If this fails (no tags yet): the range is the full history — use HEAD as the range for the log/diff commands below, and introduce the note as the first release when you present it.
• Otherwise the range is <latest>..HEAD.

Then:

git rev-list --count <range>

If the count is 0, report that there is nothing to release since <latest> and stop.

Step 3 — Collect the material

git log --no-merges --pretty=format:'%h %s%n%b---' <range>
git diff --stat <range>

Merge commits are excluded: this repo does not squash, so the PR merge commits carry nothing the branch commits do not. Use --stat, not the full diff — the commit subjects and bodies carry the intent, and the stat keeps the subagent input bounded.