Agent skill

E2E Coverage Analyzer

by shenjingnan in shenjingnan/xiaozhi-client

分析当前分支 git 改动,检查 e2e 测试用例覆盖情况,并可补充缺失的测试用例. An agent skill from shenjingnan/xiaozhi-client.

MITAuto-check passedTesting & QA

Install E2E Coverage Analyzer

skills CLI
$ npx skills add shenjingnan/xiaozhi-client --skill e2e-coverage-analyzer -a claude-code

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

GitHub CLI
$ gh skill install shenjingnan/xiaozhi-client e2e-coverage-analyzer --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/shenjingnan/xiaozhi-client.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/e2e-coverage-analyzer .claude/skills/e2e-coverage-analyzer && 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
e2e-coverage-analyzer
GitHub stars
341
Token cost
~954 tokens
SKILL.md length
182 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

分析当前分支 git 改动,检查 e2e 测试用例覆盖情况,并可补充缺失的测试用例. An agent skill from shenjingnan/xiaozhi-client.

  • Works in 3 steps: 过滤核心逻辑文件:从改动文件列表中排除以下非逻辑文件类型 → 识别功能点:对每个核心逻辑文件,结合 git diff… → 输出改动分析报告,格式如下
  • Tasks that involve End-to-end testing
  • SKILL.md covers 上下文, 现有 e2e 测试用例清单, 你的任务 and 注意事项
  • Calls git

What it does

E2E Coverage Analyzer is an agent skill from shenjingnan/xiaozhi-client. 分析当前分支 git 改动,检查 e2e 测试用例覆盖情况,并可补充缺失的测试用例

Its SKILL.md is about 950 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 Git. The licence is MIT.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/e2e-coverage-analyzer”

Requirements

  • Docker
  • Pre-approved tools (allowed-tools): Bash(git diff:*), Bash(git --no-pager diff:*), Bash(git merge-base:*), Bash(git branch --show-current:*), Bash(ls:*), Bash(find:*), Read, Glob, Grep, Write, Bash(mkdir:*)

Workflow steps

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

  1. 过滤核心逻辑文件:从改动文件列表中排除以下非逻辑文件类型
  2. 识别功能点:对每个核心逻辑文件,结合 git diff 的实际改动内容,分析其涉及的功能维度
  3. 输出改动分析报告,格式如下

What it can do on your machine

Read from SKILL.md and the folder at commit fe3c382. 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 diff:*)
    • Bash(git --no-pager diff:*)
    • Bash(git merge-base:*)
    • Bash(git branch --show-current:*)
    • Bash(ls:*)
    • Bash(find:*)
    • Read
    • Glob
    • Grep
    • Write

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    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

E2E Coverage Analyzer loads about 954 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 182 words of instructions outside code blocks.

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

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 shenjingnan/xiaozhi-client at commit fe3c382, republished under its MIT licence (© shenjingnan). 182 words, ~954 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-coverage-analyzer/SKILL.md (or your agent's skills folder).
name
e2e-coverage-analyzer
description
分析当前分支 git 改动,检查 e2e 测试用例覆盖情况,并可补充缺失的测试用例
allowed-tools
Bash(git diff:*), Bash(git --no-pager diff:*), Bash(git merge-base:*), Bash(git branch --show-current:*), Bash(ls:*), Bash(find:*), Read, Glob, Grep, Write, Bash(mkdir:*)

E2E 覆盖率分析器

分析当前分支相对于 main 的改动,评估 tests/e2e/ 中现有测试用例是否足以覆盖改动涉及的功能点。

上下文

  • 当前分支: !git branch --show-current
  • 分叉点 commit: !git merge-base main HEAD
  • 改动文件列表: !git --no-pager diff --name-only main...HEAD
  • 改动内容摘要(统计): !git --no-pager diff --stat main...HEAD
  • 改动详细内容: !git --no-pager diff main...HEAD

现有 e2e 测试用例清单

!find tests/e2e -maxdepth 1 -type d ! -path tests/e2e | sort

你的任务

按以下四个阶段执行,每个阶段输出清晰的中文报告。


阶段一:改动分析
  1. 过滤核心逻辑文件:从改动文件列表中排除以下非逻辑文件类型:

    • 配置文件:*.config.*, *.env*, tsconfig*.json, .eslintrc*, .prettierrc*
    • 类型定义文件:*.d.ts, types/*.ts, interfaces/*.ts
    • 文档和说明文件:*.md, CHANGELOG*, LICENSE*
    • 锁定文件:package-lock.json, pnpm-lock.yaml, yarn.lock
    • CI/CD 配置:.github/**, .gitlab-ci*, Dockerfile*, docker-compose*
    • 测试文件本身:**/*.test.ts, **/*.spec.ts, tests/**, __tests__/**

    保留以下类型的文件作为核心逻辑文件:

    • src/web/** 下的组件、页面、hooks、store、工具函数
    • src/server/** 下的服务、路由、控制器、中间件、处理器
    • src/ 下各模块的源码逻辑文件
  2. 识别功能点:对每个核心逻辑文件,结合 git diff 的实际改动内容,分析其涉及的功能维度:

    • 页面/路由:涉及哪个页面或路由(如 /dashboard)
    • UI 组件:涉及哪些 UI 组件(如 MCP 工具表格、对话框、表单等)
    • 交互行为:涉及的点击、输入、切换、拖拽等用户操作
    • 数据流:涉及的数据请求、状态变更、事件处理
    • 视觉呈现:涉及的新增/修改的 UI 元素、样式变化
  3. 输出改动分析报告,格式如下:

    === 改动分析报告 ===
    
    核心逻辑文件(共 N 个):
    1. src/web/pages/Dashboard.tsx
       - 涉及页面:Dashboard 页面
       - 涉及功能点:新增状态卡片 X、修改表格列 Y
    
    排除的非逻辑文件(共 M 个):
    - package.json(依赖变更)
    ...

阶段二:覆盖匹配
  1. 读取所有现有 e2e 测试用例:遍历 tests/e2e/ 下每个子目录中的 test.md 文件,提取每个用例覆盖的功能点关键词。

  2. 建立映射关系:将阶段一识别的功能点与现有测试用例进行匹配。匹配规则:

    • 精确匹配:测试用例名称或步骤明确提及了改动的功能点
    • 关联匹配:测试用例覆盖了改动所在的页面/组件区域,虽然未直接测试该具体改动,但执行路径会经过相关代码
    • 无匹配:改动涉及的功能点没有任何测试用例覆盖
  3. 输出覆盖匹配报告,格式如下:

    === 覆盖匹配报告 ===
    
    已覆盖的功能点:
    | 功能点 | 匹配测试用例 | 匹配类型 |
    |--------|-------------|---------|
    | Dashboard 页面加载 | 测试Dashboard页面加载 | 精确匹配 |
    
    缺少覆盖的功能点:
    | 功能点 | 涉及文件 | 风险等级 |
    |--------|---------|---------|
    | 新增的 XXX 功能 | src/web/components/XXX.tsx | 高 |
    
    覆盖率总结:
    - 总功能点数:N
    - 已覆盖:M(X%)
    - 未覆盖:K(Y%)

    风险等级判定标准:

    • 高:涉及新的用户可见功能或交互流程变更
    • 中:涉及已有功能的逻辑修改或边界条件变化
    • 低:涉及内部实现优化、重构、错误处理改进

阶段三:结论与建议

根据覆盖匹配结果输出结论:

如果全部覆盖(覆盖率 100%):

=== 结论 ✅ ===

当前分支的所有改动均有对应的 e2e 测试用例覆盖:

[列出所有匹配关系]

建议:可以直接提交 PR,或在提交前运行 /e2e 执行全量测试验证。

如果存在未覆盖项:

=== 结论 ⚠️ ===

当前分支存在 N 个缺少 e2e 覆盖的功能点:

[高优先级]
1. [功能点描述] — 涉及文件:xxx

[中优先级]
2. ...

是否需要为这些缺失的功能点创建新的 e2e 测试用例?
回复"是"将继续创建,回复"否"则仅保留上述报告。

特殊情况处理:

  • 如果当前分支与 main 无差异(无改动),直接提示用户并退出
  • 如果改动仅涉及非逻辑文件(纯配置、文档等),提示用户无需 e2e 覆盖并退出

阶段四:创建测试用例(仅在用户确认后执行)

当用户确认需要补充测试用例时:

  1. 确定要创建的测试用例列表:按风险等级从高到低排列。

  2. 为每个缺失的功能点创建 e2e 测试用例,遵循以下规范:

    a. 目录命名:使用中文 测试<功能描述> 格式,例如:

    • tests/e2e/测试新功能名称/

    b. test.md 格式:

    markdown
    ## 前置条件(可选)
    如有特殊前置条件在此说明
    
    ## 测试步骤
    1. 打开页面 http://localhost:9999/dashboard
    2. 等待页面加载完成
    3. [具体的操作步骤]
    4. 截图(关键状态描述)
    5. [验证断言]

    c. 编写原则:

    • 每个步骤是单一、可执行的原子操作
    • 使用元素的可辨识特征定位(title、placeholder、文本内容、图标描述)
    • 关键状态变化后必须截图
    • 必须包含明确的验证断言
    • 如需清理测试数据,在最后一步说明

    d. 参考现有用例的风格:参考已有的测试用例写法保持一致

  3. 输出创建结果报告:

    === 测试用例创建报告 ===
    
    已创建以下 e2e 测试用例:
    
    1. tests/e2e/测试XXX/test.md
       - 覆盖功能点:...
       - 步骤数:N
    
    创建完成后可使用以下命令执行:
    /e2e tests/e2e/测试XXX

注意事项

  • 本技能只进行分析和测试用例创建,不执行测试。执行测试请使用 /e2e 命令。
  • 所有输出使用中文。
  • 分析时重点关注用户可感知的功能变化,不过度追求理论上的完美覆盖。

© shenjingnan, 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/e2e-coverage-analyzer of shenjingnan/xiaozhi-client.

Open the folder on GitHubat commit fe3c382

Compare with similar skills

E2E Coverage Analyzer 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.

E2E Coverage Analyzer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Coverage Analyzer this skillshenjingnan/xiaozhi-client341—~954Automated safety check: PassMIT
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Nemoclaw Maintainer Fix E2E FailuresNVIDIA/NemoClaw23k—~2.6kAutomated safety check: PassApache-2.0
Releaselycorp-jp/sim-use1.4k—~1.7kAutomated safety check: PassApache-2.0
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0
Test Pyramidkubernetes-sigs/agent-sandbox4.2k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes
  • Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Release

    lycorp-jp/sim-use

    Cut a sim-use release end-to-end. An agent skill from lycorp-jp/sim-use.

    1.4k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Pyramid

    kubernetes-sigs/agent-sandbox

    Official

    Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need…

    4.2k GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check passed
  • E2E Test

    crowdin/crowdin-api-client-js

    Run end-to-end tests against the real Crowdin or Crowdin Enterprise API using credentials from .env.

    139 GitHub stars~893 tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from shenjingnan/xiaozhi-client

All 16 skills in this repo
  • Fix Comment

    shenjingnan/xiaozhi-client

    GitHub 评论修复技能,用于获取 PR 的 Copilot 评论并分析修复问题. An agent skill from shenjingnan/xiaozhi-client.

    341 GitHub stars~873 tokensUpdated 1 mo ago
    Auto-check passed
  • API Docs

    shenjingnan/xiaozhi-client

    文档自动生成

    341 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • CI Validator

    shenjingnan/xiaozhi-client

    CI检查验证和质量保障

    341 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Commit

    shenjingnan/xiaozhi-client

    生成代码评审友好的 commit 信息

    341 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Dev Workflow Checker

    shenjingnan/xiaozhi-client

    开发流程检查技能,确保代码修改后执行必要的质量检查

    341 GitHub stars~464 tokensUpdated 1 mo ago
    Auto-check passed
  • Docs Creator

    shenjingnan/xiaozhi-client

    文档创建技能,用于创建标准化的项目文档

    341 GitHub stars~614 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about E2E Coverage Analyzer

What does E2E Coverage Analyzer do?

分析当前分支 git 改动,检查 e2e 测试用例覆盖情况,并可补充缺失的测试用例. An agent skill from shenjingnan/xiaozhi-client. E2E Coverage Analyzer is an agent skill from shenjingnan/xiaozhi-client.

When should I use E2E Coverage Analyzer?

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

How do I install E2E Coverage Analyzer in Claude Code?

Run `npx skills add shenjingnan/xiaozhi-client --skill e2e-coverage-analyzer -a claude-code`. Or copy the skill folder (.agents/skills/e2e-coverage-analyzer in shenjingnan/xiaozhi-client) into .claude/skills/e2e-coverage-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install E2E Coverage Analyzer in Codex?

Run `npx skills add shenjingnan/xiaozhi-client --skill e2e-coverage-analyzer -a codex`. Or copy the skill folder (.agents/skills/e2e-coverage-analyzer in shenjingnan/xiaozhi-client) into .agents/skills/e2e-coverage-analyzer in your project. Codex loads it when a task matches its description.

Can I use E2E Coverage Analyzer 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 shenjingnan/xiaozhi-client --skill e2e-coverage-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/e2e-coverage-analyzer, .gemini/skills/e2e-coverage-analyzer, .github/skills/e2e-coverage-analyzer and .opencode/skills/e2e-coverage-analyzer in your project.

What does E2E Coverage Analyzer need to run?

Going by SKILL.md and its folder, E2E Coverage Analyzer needs the command-line tools its instructions call (git). Our summary lists: Docker. Its frontmatter pre-approves these tools: Bash(git diff:*), Bash(git --no-pager diff:*), Bash(git merge-base:*), Bash(git branch --show-current:*), Bash(ls:*), Bash(find:*), Read, Glob, Grep, Write, Bash(mkdir:*).

Does E2E Coverage Analyzer 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 E2E Coverage Analyzer 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 E2E Coverage Analyzer use?

E2E Coverage Analyzer 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 E2E Coverage Analyzer use?

About 954 tokens (SKILL.md is roughly 3.8k 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 E2E Coverage Analyzer?

Skills that share tags, products or a category with E2E Coverage Analyzer: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Nemoclaw Maintainer Fix E2E Failures (NVIDIA/NemoClaw, 23k stars), Release (lycorp-jp/sim-use, 1.4k stars) and Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Coverage Analyzer?

shenjingnan (a GitHub user) maintains it in shenjingnan/xiaozhi-client, which has 341 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 3, 2026.

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