Official agent skill

Go Redis Client Test Runner

Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

OfficialBSD-2-ClauseAuto-check passedTesting & QA

Install Go Redis Client Test Runner

skills CLI

$ npx skills add redis/go-redis --skill testing -a claude-code

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

GitHub CLI

$ gh skill install redis/go-redis testing --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/go-redis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/testing .claude/skills/testing && 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/

Paste into Claude Code

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .claude/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/redis/go-redis/tree/master/.claude/skills/testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add redis/go-redis --skill testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install redis/go-redis testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/redis/go-redis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/testing .agents/skills/testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .agents/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add redis/go-redis --skill testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install redis/go-redis testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/redis/go-redis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/testing .cursor/skills/testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .cursor/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/redis/go-redis.git --path .claude/skills/testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add redis/go-redis --skill testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install redis/go-redis testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/redis/go-redis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/testing .gemini/skills/testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .gemini/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install redis/go-redis testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add redis/go-redis --skill testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/redis/go-redis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/testing .github/skills/testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .github/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add redis/go-redis --skill testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install redis/go-redis testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/redis/go-redis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/testing .opencode/skills/testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "testing" agent skill from https://github.com/redis/go-redis/tree/master/.claude/skills/testing into .opencode/skills/testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: testing
GitHub stars: 22k
Token cost: ~786 tokens
SKILL.md length: 195 words
Files: 1
Skills in repo: 5
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: BSD-2-Clause

At a glance

Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

Running the full go-redis suite or a single Ginkgo spec such as the cluster tests
SKILL.md covers Make targets, E2E (maintenance notifications), Env knobs (passed through the… and Running a single test, plus 1 more section
Calls make and go
Bringing the Docker test stack up or tearing it down

What it does

Tests in this repository run against a Redis stack started through Docker Compose, where profiles such as standalone, cluster, sentinel, all and e2e decide which services come up. The skill lists the make targets for starting and stopping that stack and for the full run, and notes that the Makefile loops over every go.mod directory for CI tests and module tidying.

Running one test depends on the suite. The root suite is Ginkgo-based, so go test -run TestGinkgoSuite needs the -ginkgo.focus flag to pick a spec, while plain Go tests under directories such as internal or maintnotifications take the usual go test -run, with -race when wanted. The e2e maintenance-notifications suite needs an extra cae-resp-proxy service, and a logic-only target skips the proxy.

Environment variables steer the run: REDIS_VERSION sets the image tag and the version-gating helpers, CLIENT_LIBS_TEST_IMAGE gives a full image reference, RE_CLUSTER points tests at a Redis Enterprise cluster, RCE_DOCKER marks Redis CE in Docker, and REDIS_PORT overrides the standalone port, 6380 by default. Version-specific tests are gated with SkipBeforeRedisVersion and SkipAfterRedisVersion instead of being skipped for the whole suite.

When your agent uses it

Running the full go-redis suite or a single Ginkgo spec such as the cluster tests
Bringing the Docker test stack up or tearing it down
Running the maintenance-notifications e2e tests, including the subset that needs no proxy
Testing against a particular Redis version or a Redis Enterprise cluster

Example prompts

“Run only the cluster specs in the go-redis suite.”
“Start the Docker test stack, run make test, and shut everything down afterwards.”
“Run the e2e logic tests that do not need the proxy.”
“Test the connection pool package with the race detector against Redis 8.8.”

Requirements

Docker with Docker Compose
Go toolchain and make

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 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:
- make
- go
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Client Test Runner loads about 786 tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 195 words of instructions outside code blocks.

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

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/go-redis at commit 6f2b263, republished under its BSD-2-Clause licence (© redis). 195 words, ~786 tokens.

Download SKILL.mdSave it as .claude/skills/testing/SKILL.md (or your agent's skills folder).

name: testing
description: Use when running go-redis tests of any kind — the full suite, a single test, or a filtered/focused subset (e.g. only cluster, sentinel, or pool specs); bringing up or tearing down the Docker test stack; the e2e maintenance-notifications suite (including the proxy-free logic tests); building or formatting; or setting the REDIS_VERSION / RE_CLUSTER / REDIS_PORT knobs that drive the test image and version gating. Covers how to focus a Ginkgo spec and how to run plain go tests.

Running tests, builds, and the Docker stack

Tests run against a Redis stack started via Docker Compose. Profiles in docker-compose.yml control which services come up (standalone, cluster, sentinel, all, e2e, …).

Make targets

make docker.start          # bring up the full test stack (profile: all)
make docker.stop
make test                  # docker.start -> test.ci -> docker.stop
make test.ci               # run tests assuming containers are already up
make test.ci.skip-vectorsets   # used when REDIS_VERSION < 8
make bench                 # go test -bench=. (root module only)
make fmt                   # gofumpt + goimports (-local github.com/redis/go-redis)
make build
make go_mod_tidy           # go mod tidy across every module

The Makefile iterates over every go.mod (GO_MOD_DIRS) for test.ci, go_mod_tidy, etc.

E2E (maintenance notifications)

Needs an extra cae-resp-proxy service:

make test.e2e              # auto-starts the e2e profile, runs ./maintnotifications/e2e/, tears down
make test.e2e.docker       # subset that runs inside docker
make test.e2e.logic        # logic-only tests, no proxy required

Env knobs (passed through the Makefile)

REDIS_VERSION — e.g. 8.8. Drives both the test image tag and main_test.go version-gating helpers (SkipBeforeRedisVersion / SkipAfterRedisVersion).
CLIENT_LIBS_TEST_IMAGE — full image ref, e.g. redislabs/client-libs-test:8.8-m03. (To change the default tag, use the update-ci-image skill — it lives in several files.)
RE_CLUSTER=true — point tests at a Redis Enterprise cluster instead of the docker-compose stack. The suite then skips ring/sentinel/TLS-cluster setup.
RCE_DOCKER=true — using Redis CE in docker (default for make test).
REDIS_PORT — override the default standalone port (6380) used by main_test.go.

Running a single test

The root suite is Ginkgo-based (bsm/ginkgo + bsm/gomega forks). go test -run matches the Go-level wrapper, so to focus a Ginkgo spec use the Ginkgo focus flag:

go test -run TestGinkgoSuite . -ginkgo.focus="ZAdd"
go test -run TestGinkgoSuite . -ginkgo.focus="cluster"

Plain go test-style tests (most files outside the Ginkgo suite, e.g. internal/..., maintnotifications/...) work the usual way:

go test -run TestConnStateMachine ./internal/pool/...
go test -race -run TestCircuitBreaker ./maintnotifications/...

Version-gating

Gate Redis-version-specific tests with SkipBeforeRedisVersion / SkipAfterRedisVersion (driven by REDIS_VERSION) rather than skipping at the suite level.

Files

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

Open the folder on GitHubat commit 6f2b263

Compare with similar skills

Go Redis Client Test Runner 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.

Go Redis Client Test Runner compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Go Redis Client Test Runner this skillredis/go-redis	22k	—	~786	Automated safety check: Pass	BSD-2-Clause	yesterday
E2Eopenathleteorg/openathlete	100	—	~675	Automated safety check: Pass	AGPL-3.0	yesterday
PR TestElite588/AUTOGPT	103	—	~9.4k	Automated safety check: Notes	Custom licence	5 mo ago
Tgf Server Devthkhxm/tgf	128	—	~1.3k	Automated safety check: Notes	MIT	2 mo ago
MongoDB Source Connector E2E Harnessairbytehq/airbyte	22k	—	~1.9k	Automated safety check: Pass	Custom licence	today
Airbyte Postgres Source E2E Testsairbytehq/airbyte	22k	—	~2.5k	Automated safety check: Pass	Custom licence	today

Similar skills

E2E
openathleteorg/openathlete
Run, debug or extend the OpenAthlete Playwright end-to-end tests, which exercise the production Docker images (API, worker, web, PostgreSQL, Redis) through the API and a real browser on desktop and…
100 GitHub stars~675 tokensUpdated yesterday
Testing & QAAuto-check passed
PR Test
Elite588/AUTOGPT
E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls.
103 GitHub stars~9.4k tokensUpdated 5 mo ago
Testing & QAAuto-check: notes
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
MongoDB Source Connector E2E Harness
airbytehq/airbyte
Official
Starts a throwaway MongoDB 7.0 replica set and runs the Airbyte spec, check, discover and read commands against source-mongodb-v2 images for local end-to-end testing.
22k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed
Airbyte Postgres Source E2E Tests
airbytehq/airbyte
Official
Starts a local PostgreSQL 16 container, loads SQL fixtures and runs the Airbyte spec, check, discover and read commands against a chosen source-postgres image.
22k GitHub stars~2.5k tokensUpdated today
Testing & QAAuto-check passed
Postgres CDC E2E Test Harness
airbytehq/airbyte
Official
Reproduces PostgreSQL logical-decoding CDC behavior for Airbyte's source-postgres connector on a local backend, with CDC fixtures, a catalog and smoke case scripts.
22k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed

Questions about Go Redis Client Test Runner

What does Go Redis Client Test Runner do?

Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables. Tests in this repository run against a Redis stack started through Docker Compose, where profiles such as standalone, cluster, sentinel, all and e2e decide which services come up.mod directory for CI tests and module tidying.

When should I use Go Redis Client Test Runner?

Go Redis Client Test Runner fits situations like: running the full go-redis suite or a single Ginkgo spec such as the cluster tests; bringing the Docker test stack up or tearing it down; running the maintenance-notifications e2e tests, including the subset that needs no proxy; testing against a particular Redis version or a Redis Enterprise cluster.

How do I install Go Redis Client Test Runner in Claude Code?

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

How do I install Go Redis Client Test Runner in Codex?

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

Can I use Go Redis Client Test Runner 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/go-redis --skill testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing, .gemini/skills/testing, .github/skills/testing and .opencode/skills/testing in your project.

What does Go Redis Client Test Runner need to run?

Going by SKILL.md and its folder, Go Redis Client Test Runner needs the command-line tools its instructions call (make and go). Our summary lists: Docker with Docker Compose; Go toolchain and make.

Does Go Redis Client Test Runner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Go Redis Client Test Runner 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 Go Redis Client Test Runner use?

Go Redis Client Test Runner is published under the BSD-2-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Go Redis Client Test Runner use?

About 786 tokens (SKILL.md is roughly 3.1k 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 Go Redis Client Test Runner?

Skills that share tags, products or a category with Go Redis Client Test Runner: E2E (openathleteorg/openathlete, 100 stars), PR Test (Elite588/AUTOGPT, 103 stars), Tgf Server Dev (thkhxm/tgf, 128 stars) and MongoDB Source Connector E2E Harness (airbytehq/airbyte, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Go Redis Client Test Runner?

redis (a GitHub organization, an official publisher) maintains it in redis/go-redis, which has 22,257 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

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

Go Redis Client Test Runner

Install Go Redis Client Test Runner

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Running tests, builds, and the Docker stack

Make targets

E2E (maintenance notifications)

Env knobs (passed through the Makefile)

Running a single test

Version-gating

Files

Compare with similar skills

Similar skills

E2E

PR Test

Tgf Server Dev

MongoDB Source Connector E2E Harness

Airbyte Postgres Source E2E Tests

Postgres CDC E2E Test Harness

More from redis/go-redis

Add Redis Command to go-redis

Go-Redis Release Preparation

Redis Test Image Update

Commit Style for go-redis

Questions about Go Redis Client Test Runner

Install Go Redis Client Test Runner

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Running tests, builds, and the Docker stack

Make targets

E2E (maintenance notifications)

Env knobs (passed through the Makefile)

Running a single test

Version-gating

Files

Compare with similar skills

Similar skills

More from redis/go-redis

Related

Questions about Go Redis Client Test Runner