Go-Redis Release Preparation

What it does

When your agent uses it

• Cutting a new go-redis version
• Writing the RELEASE-NOTES.md entry for a release
• Updating the go-redis dependency version in submodule go.mod files
• Choosing the next semver from what merged since the last release

Example prompts

• “Prepare the next go-redis release and tell me whether it should be a patch or a minor.”
• “Write the RELEASE-NOTES.md entry from the PRs merged since the last tag.”
• “Bump the submodule go.mod files to the new version and run the tag dry run.”

Requirements

• Git and the GitHub CLI (gh)
• A checkout of redis/go-redis
• Pre-approved tools (allowed-tools): Bash(git describe:*), Bash(gh pr list:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

1. 1Pick the next version
2. 2Find the last release and gather changes
3. 3Write the release notes
4. 4Bump versions
5. 5Verify (dry run only)
6. 6Hand off

What it can do on your machine

Read from SKILL.md and the folder at commit 6f2b263. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash(git describe:*)
  • Bash(gh pr list:*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • git
  • gh
  • make
  • go

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Go-Redis Release Preparation loads about 1.1k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 442 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~135

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from redis/go-redis at commit 6f2b263, republished under its BSD-2-Clause licence (© redis). 442 words, ~1,072 tokens.

name

prepare-release

description

Use when preparing a go-redis release — cutting a new version, bumping version.go, updating the go-redis dependency version in submodule go.mod files, or writing the RELEASE-NOTES.md entry for a new vX.Y.Z. Covers choosing the next semver, finding the last release and gathering merged PRs since then, the release-notes format and what to exclude, running scripts/release.sh to bump versions, and verifying with the scripts/tag.sh dry-run. Does NOT create tags, push, or commit — publishing stays a manual maintainer step.

allowed-tools

Bash(git describe:*), Bash(gh pr list:*)

grep 'return' version.go        # e.g. return "9.21.0"

LAST=$(git describe --tags --abbrev=0 --match 'v[0-9]*')   # e.g. v9.21.0
git log "$LAST"..HEAD --oneline
gh pr list --state merged --limit 100 \
  --json number,title,author,mergedAt,url --search "merged:>=<last-release-date>"

TAG=vX.Y.Z ./scripts/release.sh

./scripts/tag.sh vX.Y.Z         # DRY RUN — must pass cleanly; never add -t here
make build
git diff --stat                 # review version.go, submodule go.mod, RELEASE-NOTES.md

© redis, BSD-2-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prepare-release of redis/go-redis.

Open the folder on GitHubat commit 6f2b263