Agent skill

Release E2E

by nidjbs in nidjbs/go-ai-gateway

发布前强制 e2e 验证门禁。在每次发布/打 tag/部署生产之前必须运行,验证网关核心能力与可用性。当用户提到"发布"、"准备 release"、"打 tag"、"发布前验证"时使用。

MITAuto-check passedTesting & QA

Install Release E2E

skills CLI
$ npx skills add nidjbs/go-ai-gateway --skill release-e2e -a claude-code

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

GitHub CLI
$ gh skill install nidjbs/go-ai-gateway release-e2e --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/nidjbs/go-ai-gateway.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-e2e .claude/skills/release-e2e && 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
release-e2e
GitHub stars
126
Token cost
~523 tokens
SKILL.md length
198 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

发布前强制 e2e 验证门禁。在每次发布/打 tag/部署生产之前必须运行,验证网关核心能力与可用性。当用户提到"发布"、"准备 release"、"打 tag"、"发布前验证"时使用。

  • Works in 3 steps: 确认工作区干净(git… → 运行统一门禁 → 看到 All release checks passed — safe to…
  • Tasks that involve End-to-end testing
  • SKILL.md covers 执行步骤, 核心能力清单(必须全部通过), 通过标准 and 失败处理, plus 1 more section
  • Calls git and go

What it does

Release E2E is an agent skill from nidjbs/go-ai-gateway. 发布前强制 e2e 验证门禁。在每次发布/打 tag/部署生产之前必须运行,验证网关核心能力与可用性。当用户提到"发布"、"准备 release"、"打 tag"、"发布前验证"时使用。

Its SKILL.md is about 520 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 Testing & QA, covering End-to-end testing. It works with Docker. The repository describes itself as: go lightweight ai-gateway. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “准备 release”
  • “/release-e2e”

Requirements

  • Python 3
  • Docker

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 确认工作区干净(git status),必要时先提交当前改动(脚本运行的是工作区代码)。
  2. 运行统一门禁
  3. 看到 All release checks passed — safe to release. 且退出码为 0,才允许继续发布动作。

What it can do on your machine

Read from SKILL.md and the folder at commit f875f57. 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
    • 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, 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

Release E2E loads about 523 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 198 words of instructions outside code blocks.

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

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 nidjbs/go-ai-gateway at commit f875f57, republished under its MIT licence (© nidjbs). 198 words, ~523 tokens.

Download SKILL.mdSave it as .claude/skills/release-e2e/SKILL.md (or your agent's skills folder).
name
release-e2e
description
发布前强制 e2e 验证门禁。在每次发布/打 tag/部署生产之前必须运行,验证网关核心能力与可用性。当用户提到"发布"、"准备 release"、"打 tag"、"发布前验证"时使用。

Release E2E 验证门禁

每次发布之前必须执行本 skill,验证网关核心能力全部通过后才能发布。任何一步失败即视为发布阻塞。

执行步骤

  1. 确认工作区干净(git status),必要时先提交当前改动(脚本运行的是工作区代码)。

  2. 运行统一门禁:

    bash
    ./scripts/release_check.sh

    该脚本按顺序执行:gofmt → go vet → go test → build → e2e.sh(核心能力)→ e2e_apikey.sh(认证/限流/配额)→ e2e_release.sh(策略/DLP/幂等/Admin/熔断)→ docker build(可选)。

  3. 看到 All release checks passed — safe to release. 且退出码为 0,才允许继续发布动作。

核心能力清单(必须全部通过)

类别覆盖内容验证脚本
代码质量gofmt / go vet / 全量单测 / 编译release_check.sh
操作端点healthz / livez / readyz / metrics / versione2e.sh
认证static token、api-key、错误 key 401e2e.sh + e2e_apikey.sh
模型 & 路由/v1/models、alias 解析、未知模型 400e2e.sh
Chat非流式、多轮、工具调用e2e.sh
Chat 流式SSE 正常 / 首 chunk 后不降级 / 超时e2e.sh
Anthropic 适配原生协议 chat / tool / stream / retry / failovere2e.sh
弹性重试、失败降级(openai + anthropic + stream)e2e.sh
Embeddings单输入、多输入、降级e2e.sh
用量sqlite 持久化、usage 落库e2e.sh
Guardrails注入 / 越狱 / 中文 / 角色覆盖 429e2e.sh
限流 & 配额rps 限流、每日 token 配额、Retry-Aftere2e_apikey.sh
路由策略loadbalance 加权分布、least_latency 切快e2e_release.sh
输出 DLPPII mask / reject(email、phone)e2e_release.sh
幂等Idempotency-Key 重放不重复计费e2e_release.sh
Admin运行时 revoke key → 401、revoked 列表、usage 查询e2e_release.sh
熔断故障后打开、不再调用上游e2e_release.sh

通过标准

  • ./scripts/release_check.sh 退出码为 0。
  • 输出包含 All release checks passed — safe to release.。
  • 三个 e2e 脚本各自打印 All ... cases passed.。

失败处理

  1. 停下,不得发布、不得打 tag、不得构建发布镜像。
  2. 定位失败步骤:脚本输出显示卡在哪个 [N/8] 步骤;e2e 失败时 scripts/e2e*.sh 会自动 dump 相关进程日志(或设置 KEEP_E2E_LOGS=1 保留临时目录)。
  3. 把失败原因和日志摘要报告给用户,修复后重跑整个 release_check.sh(不要只重跑失败的那一步)。
  4. 全部通过后才继续发布。

注意事项

  • 需要 Go、Bash、curl、Python 3(e2e 脚本依赖);docker 可选(无 docker 时自动跳过容器构建)。
  • e2e 脚本会在随机端口起真实 gateway + mock 上游,运行期间不要占用 8080/8081。
  • 若改动影响 Redis 分布式路径,发布前建议额外用 go test -race ./internal/... 验证并发正确性。

© nidjbs, 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 .claude/skills/release-e2e of nidjbs/go-ai-gateway.

Open the folder on GitHubat commit f875f57

Compare with similar skills

Release E2E 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.

Release E2E compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release E2E this skillnidjbs/go-ai-gateway126—~523Automated safety check: PassMIT
MongoDB Source Connector E2E Harnessairbytehq/airbyte22k—~1.9kAutomated safety check: PassCustom licence
source-mssql E2E Test Harnessairbytehq/airbyte22k—~4.4kAutomated safety check: PassCustom licence
Airbyte source-mysql E2E Testsairbytehq/airbyte22k—~2.6kAutomated safety check: PassCustom licence
Go Redis Client Test Runnerredis/go-redis22k—~786Automated safety check: PassBSD-2-Clause
E2E TestingOpenHands/OpenHands90k—~308Automated safety check: PassMIT

Similar skills

  • 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
  • Official

    Stands up a throwaway local SQL Server 2022 backend, applies SQL fixtures and runs Airbyte spec, check, discover and read against source-mssql images.

    22k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Stands up a throwaway local MySQL 8.0 backend, applies SQL fixtures and sweeps the Airbyte spec, check, discover and read commands against a source-mysql image.

    22k GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    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.

    22k GitHub stars~786 tokensUpdated today
    Testing & QAAuto-check passed
  • E2E Testing

    OpenHands/OpenHands

    This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E…

    90k GitHub stars~308 tokensUpdated today
    Testing & QAAuto-check passed
  • 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

Works with

Categories

Questions about Release E2E

What does Release E2E do?

发布前强制 e2e 验证门禁。在每次发布/打 tag/部署生产之前必须运行,验证网关核心能力与可用性。当用户提到"发布"、"准备 release"、"打 tag"、"发布前验证"时使用。. Release E2E is an agent skill from nidjbs/go-ai-gateway.

When should I use Release E2E?

Release E2E fits situations like: tasks that involve End-to-end testing.

How do I install Release E2E in Claude Code?

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

How do I install Release E2E in Codex?

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

Can I use Release E2E 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 nidjbs/go-ai-gateway --skill release-e2e -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-e2e, .gemini/skills/release-e2e, .github/skills/release-e2e and .opencode/skills/release-e2e in your project.

What does Release E2E need to run?

Going by SKILL.md and its folder, Release E2E needs the command-line tools its instructions call (git and go). Our summary lists: Python 3; Docker.

Does Release E2E access the network?

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

Is Release E2E 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 Release E2E use?

Release E2E 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 Release E2E use?

About 523 tokens (SKILL.md is roughly 2.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 Release E2E?

Skills that share tags, products or a category with Release E2E: MongoDB Source Connector E2E Harness (airbytehq/airbyte, 22k stars), source-mssql E2E Test Harness (airbytehq/airbyte, 22k stars), Airbyte source-mysql E2E Tests (airbytehq/airbyte, 22k stars) and Go Redis Client Test Runner (redis/go-redis, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release E2E?

nidjbs (a GitHub user) maintains it in nidjbs/go-ai-gateway, which has 126 GitHub stars. The repository was last updated on September 7, 2026.

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