Official agent skill

Bump Test Image

by redis in redis/node-redis

Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULTDOCKERCONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream.

OfficialMITAuto-check passedDatabases

Install Bump Test Image

skills CLI
$ npx skills add redis/node-redis --skill bump-test-image -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install redis/node-redis bump-test-image --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/redis/node-redis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-test-image .claude/skills/bump-test-image && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bump-test-image
GitHub stars
18k
Token cost
~1.4k tokens
SKILL.md length
557 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULTDOCKERCONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream.

  • Works in 7 steps: Sync master from upstream → Reset the work branch → Edit the shared default config → …
  • Tasks that involve Containers
  • SKILL.md covers Inputs, Step 1 — Sync master from…, Step 2 — Reset the work branch and Step 3 — Edit the shared…, plus 4 more sections
  • Calls git and gh

What it does

Bump Test Image is an agent skill from redis/node-redis, published by the product's own GitHub organization. Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULTDOCKERCONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream. User-invoked only.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases, covering Containers and Pull requests. It works with Redis and Docker. The licence is MIT.

When your agent uses it

  • Tasks that involve Containers
  • Tasks that involve Pull requests

Example prompts

  • “/bump-test-image”

Requirements

  • Docker

Workflow steps

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

  1. Sync master from upstream
  2. Reset the work branch
  3. Edit the shared default config
  4. Update the CI matrix
  5. Verify
  6. Commit
  7. Force-push and PR

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    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

Bump Test Image loads about 1.4k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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/node-redis at commit bba9381, republished under its MIT licence (© redis). 557 words, ~1,398 tokens.

Download SKILL.mdSave it as .claude/skills/bump-test-image/SKILL.md (or your agent's skills folder).
name
bump-test-image
description
Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULT_DOCKER_CONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream. User-invoked only.
disable-model-invocation
true
argument-hint
<image-tag> [redis-version]

Bump default docker test image

Updates the default redislabs/client-libs-test docker tag used by tests (a single shared config in @redis/test-utils), adjusts the CI matrix, commits on a freshly-reset bump-test-image branch, force-pushes it, and opens (or updates) a PR against redis/node-redis master.

Inputs

  • tag (required): the new docker tag, e.g. 8.8.0, 8.8-rc1, custom-28772936538-debian, unstable-24425681442-debian. If given as redislabs/client-libs-test:<tag>, strip the image name.
  • version (sometimes required): the Redis version the tag represents, e.g. 8.10.
    • Derivable when the tag is version-shaped: 8.8.0 → 8.8, 8.8-rc1 → 8.8, 8.8-m03 → 8.8.
    • NOT derivable for custom-* / unstable-* tags — if missing, ask the user which Redis version the tag maps to before doing anything else.

If no tag was given at all, ask for it and stop.

Step 1 — Sync master from upstream

Remotes: upstream = redis/node-redis (canonical), origin = the user's fork.

bash
git fetch upstream
git rev-parse --abbrev-ref HEAD   # remember current branch

Update local master to upstream:

  • If currently on master: git reset --hard upstream/master (only if working tree is clean — if dirty, stop and tell the user).
  • Otherwise: git fetch upstream master:master (fails safely if master has local-only commits; if it fails, stop and report).

Step 2 — Reset the work branch

bash
git checkout -B bump-test-image master

-B creates or hard-resets the branch to latest master. Any previous bump commits on it are intentionally discarded (the branch is recycled for each bump; force-push later matches this).

Step 3 — Edit the shared default config

The default image config lives in exactly ONE place:

packages/test-utils/lib/index.ts → DEFAULT_DOCKER_CONFIG:

typescript
export const DEFAULT_DOCKER_CONFIG: TestUtilsConfig = {
  dockerImageName: 'redislabs/client-libs-test',
  dockerImageTagArgument: 'redis-tag',
  dockerImageVersionArgument: 'redis-version',
  defaultDockerVersion: { tag: '<old-tag>', version: '<old-version>' }
};

Note the old tag/version, then replace them with the new values on the defaultDockerVersion line. Nothing else in the file changes.

If DEFAULT_DOCKER_CONFIG does not exist in that file (e.g. master predates the dedupe refactor), STOP and tell the user — do not fall back to editing per-package test-utils files without confirmation.

Step 4 — Update the CI matrix

File: .github/workflows/tests.yml, matrix → redis entries of the form:

yaml
          - tag: "8.8.0"
            version: "8.8"

Two cases, decided by comparing the new version with the old default version from Step 3:

  1. New Redis version (e.g. default moves 8.8 → 8.10): add a new - tag/version entry at the end of the matrix list, keeping the previous entry so CI retains coverage of the prior version.
  2. Same Redis version (rc → GA, or a newer custom build of the same version): replace the tag of the existing entry for that version; the version line stays.
Show full SKILL.md (185 more words)Show less

Step 5 — Verify

bash
grep -rn "defaultDockerVersion:" packages --include="*.ts" | grep -v dist | grep -v node_modules

Exactly one config line (in packages/test-utils/lib/index.ts) must show the new tag/version; any other hits are the type definition / JSDoc examples, not real defaults. Also confirm git diff --stat touches exactly 2 files: packages/test-utils/lib/index.ts + .github/workflows/tests.yml.

Step 6 — Commit

Fill in this template exactly (Conventional Commits):

chore(tests): bump default docker test image to <X>

Bump the default Redis test image from <old-tag> to <new-tag> (Redis
<version>) in DEFAULT_DOCKER_CONFIG, and <matrix-action> the CI matrix.
  • <X>: the human-meaningful version when the tag is version-shaped (8.10, 8.8.0, 8.8-rc1, 8.8-m03); the full tag for unstable-* builds; the version for custom-* tags (the actual tag already appears in the body as <new-tag>).
  • <matrix-action>: either add an <version> entry to (keeping prior-version coverage) or update the <version> entry in, matching what Step 4 did.

Example:

chore(tests): bump default docker test image to 8.10

Bump the default Redis test image from 8.8.0 to custom-28772936538-debian
(Redis 8.10) in DEFAULT_DOCKER_CONFIG, and add an 8.10 entry to the CI
matrix.

Keep any company-internal references (Jira/Confluence IDs, internal links) out of the commit and PR.

Step 7 — Force-push and PR

bash
git push -f origin bump-test-image

Then check for an existing open PR before creating one:

bash
gh pr list --repo redis/node-redis --head <fork-owner>:bump-test-image --state open

(<fork-owner> = GitHub owner from the origin remote URL.)

  • If a PR exists, the force-push already updated it — just report the URL. Update its title/body via gh pr edit to match the new tag.
  • Otherwise create one:
bash
gh pr create --repo redis/node-redis --base master --head <fork-owner>:bump-test-image \
  --title "<commit subject>" \
  --body "<commit body>"

Finish by reporting: old → new tag/version, matrix action taken (added vs replaced entry), and the PR URL.

© redis, MIT. 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 .agents/skills/bump-test-image of redis/node-redis.

Open the folder on GitHubat commit bba9381

Compare with similar skills

Bump Test Image next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bump Test Image compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bump Test Image this skillredis/node-redis18k—~1.4kAutomated safety check: PassMIT
Tgf Server Devthkhxm/tgf128—~1.3kAutomated safety check: NotesMIT
Cloudrun DevelopmentTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~7.2kAutomated safety check: PassMIT
Infra AuditSethGammon/Citadel923—~2.1kAutomated safety check: NotesMIT
Redis Insight Pluginredis/RedisInsight8.9k—~3.5kAutomated safety check: PassMIT
Redis Test Image Updateredis/go-redis22k—~1.5kAutomated safety check: PassBSD-2-Clause

Similar skills

  • Tgf Server Dev

    thkhxm/tgf

    基于 tgf v2(github.com/thkhxm/tgf/v2)用确定性的 tgfctl 工作流创建、验证和维护 Go 游戏服务器项目。

    128 GitHub stars~1.3k tokensUpdated 2 mo ago
    DatabasesAuto-check: notes
  • Cloudrun Development

    TencentCloudBase/CloudBase-AI-Toolkit

    CloudBase Run backend development rules (Function mode/Container mode).

    1.1k GitHub starsUsed in 1 repo~7.2k tokens
    DatabasesAuto-check passed
  • Infra Audit

    SethGammon/Citadel

    Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure.

    923 GitHub stars~2.1k tokensUpdated today
    DatabasesAuto-check: notes
  • Redis Insight Plugin

    redis/RedisInsight

    Official

    A skill your agent uses when creating, modifying, debugging, deploying, or testing Redis Insight Workbench visualization plugins, plugin manifests, package.json visualizations, activationMethod…

    8.9k GitHub stars~3.5k tokensUpdated 4 days ago
    DatabasesAuto-check passed
  • Official

    Keeps every reference to the redislabs client-libs-test image tag in sync across the Makefile, compose file, GitHub workflows and docs when a Redis test version changes.

    22k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Os Eco Dep Sync

    jayminwest/warren

    Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR.

    479 GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check passed

More from redis/node-redis

  • Runtime Behavior Probe

    redis/node-redis

    Official

    Plan and execute runtime-behavior investigations with temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports.

    18k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Implement Command

    redis/node-redis

    Official

    Add a new Redis command (or command variant) to node-redis end-to-end — the <NAME.ts Command file, its registration with JSDoc in the package commands/index.ts, and a co-located <NAME.spec.ts with…

    18k GitHub stars~5k tokensUpdated yesterday
    Auto-check passed
  • Maintainer Triage

    redis/node-redis

    Official

    Batch-triage and act on a set of node-redis PRs (or issues) by filter — fan out the maintainer-review methodology across them, present a one-word verdict plus a tldr to the user one at a time for…

    18k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Docs Sync

    redis/node-redis

    Official

    Analyze master branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/, README.md, and per-package READMEs.

    18k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Maintainer Review

    redis/node-redis

    Official

    Review a GitHub issue or pull request URL as a node-redis maintainer, with a staged assessment of whether the claim is real, practically important, already solvable with supported functionality…

    18k GitHub stars~5.5k tokensUpdated yesterday
    Auto-check passed
  • PR Draft Summary

    redis/node-redis

    Official

    Create the required PR-ready summary block, branch suggestion, title, and draft description for node-redis.

    18k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check: warnings

Works with

Questions about Bump Test Image

What does Bump Test Image do?

Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULTDOCKERCONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream. Bump Test Image is an agent skill from redis/node-redis, published by the product's own GitHub organization. Bump the default Redis docker test image (redislabs/client-libs-test) in the shared DEFAULTDOCKERCONFIG and the CI matrix, then force-push the bump-test-image branch and open a PR against upstream.

When should I use Bump Test Image?

Bump Test Image fits situations like: tasks that involve Containers; tasks that involve Pull requests.

How do I install Bump Test Image in Claude Code?

Run `npx skills add redis/node-redis --skill bump-test-image -a claude-code`. Or copy the skill folder (.agents/skills/bump-test-image in redis/node-redis) into .claude/skills/bump-test-image in your project. Claude Code loads it when a task matches its description.

How do I install Bump Test Image in Codex?

Run `npx skills add redis/node-redis --skill bump-test-image -a codex`. Or copy the skill folder (.agents/skills/bump-test-image in redis/node-redis) into .agents/skills/bump-test-image in your project. Codex loads it when a task matches its description.

Can I use Bump Test Image in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add redis/node-redis --skill bump-test-image -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-test-image, .gemini/skills/bump-test-image, .github/skills/bump-test-image and .opencode/skills/bump-test-image in your project.

What does Bump Test Image need to run?

Going by SKILL.md and its folder, Bump Test Image needs the command-line tools its instructions call (git and gh). Our summary lists: Docker.

Does Bump Test Image access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bump Test Image safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bump Test Image use?

Bump Test Image is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bump Test Image use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bump Test Image?

Skills that share tags, products or a category with Bump Test Image: Tgf Server Dev (thkhxm/tgf, 128 stars), Cloudrun Development (TencentCloudBase/CloudBase-AI-Toolkit, 1.1k stars), Infra Audit (SethGammon/Citadel, 923 stars) and Redis Insight Plugin (redis/RedisInsight, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Test Image?

redis (a GitHub organization, an official publisher) maintains it in redis/node-redis, which has 17,585 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: redis/node-redis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.