Integration E2E Testing
shinpr/claude-code-workflows
Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria.
盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug…
Install Test Collaboration
$ npx skills add qshanx/docs-governance --skill test-collaboration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qshanx/docs-governance test-collaboration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-collaboration .claude/skills/test-collaboration && rm -rf skills-srcUse ~/.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/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .claude/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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 install https://github.com/qshanx/docs-governance/tree/main/skills/test-collaborationType 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.
$ npx skills add qshanx/docs-governance --skill test-collaboration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qshanx/docs-governance test-collaboration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-collaboration .agents/skills/test-collaboration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .agents/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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.
$ npx skills add qshanx/docs-governance --skill test-collaboration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qshanx/docs-governance test-collaboration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-collaboration .cursor/skills/test-collaboration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .cursor/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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 https://github.com/qshanx/docs-governance.git --path skills/test-collaboration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add qshanx/docs-governance --skill test-collaboration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qshanx/docs-governance test-collaboration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-collaboration .gemini/skills/test-collaboration && rm -rf skills-srcUse ~/.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/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .gemini/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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.
$ gh skill install qshanx/docs-governance test-collaborationInstalls 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).
$ npx skills add qshanx/docs-governance --skill test-collaboration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-collaboration .github/skills/test-collaboration && rm -rf skills-srcUse ~/.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/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .github/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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.
$ npx skills add qshanx/docs-governance --skill test-collaboration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install qshanx/docs-governance test-collaboration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-collaboration .opencode/skills/test-collaboration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-collaboration" agent skill from https://github.com/qshanx/docs-governance/tree/main/skills/test-collaboration into .opencode/skills/test-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-collaboration", 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
test-collaboration- GitHub stars
- 132
- Token cost
- ~1.1k tokens
- SKILL.md length
- 247 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug…
- Works in 5 steps: 盘点现有测试资产 → 把需求、规则和风险转成 TEST-ID → 把 Bug 转成回归保护 → …
- Tasks that involve Integration testing
- SKILL.md covers 目标, 职责边界, 开始前读取 and 工作模式, plus 2 more sections
- Calls npm and make
What it does
Test Collaboration is an agent skill from qshanx/docs-governance. 盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug 转测试、契约测试、前后端接口测试、测试治理。English triggers: test inventory, test catalog, test gap analysis, bug-to-test, contract testing, consumer contract, provider verification, test governance.
Its SKILL.md is about 1.1k 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 Integration testing and End-to-end testing. The repository describes itself as: Claude Code、Codex 与 ChatGPT 的文档驱动开发治理插件：防文档腐烂、维护上下文与决策、契约协作、测试与回归证据。 The licence is MIT.
When your agent uses it
- Tasks that involve Integration testing
- Tasks that involve End-to-end testing
Example prompts
- “/test-collaboration”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 520696e. 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:
npmmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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
Test Collaboration loads about 1.1k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 247 words of instructions outside code blocks.
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 qshanx/docs-governance at commit 520696e, republished under its MIT licence (© qshanx). 247 words, ~1,060 tokens.
Download SKILL.mdSave it as
.claude/skills/test-collaboration/SKILL.md (or your agent's skills folder).- name
- test-collaboration
- description
- 盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug 转测试、契约测试、前后端接口测试、测试治理。English triggers: test inventory, test catalog, test gap analysis, bug-to-test, contract testing, consumer contract, provider verification, test governance.
测试协作治理（test-collaboration）
目标
用项目根目录的 TESTS.md 管理两类信息：
- 现有测试资产地图：项目已经有哪些测试、从哪里运行、保护什么。
- 必要测试点清单：哪些需求、规则、风险和 Bug 必须被测试保护，当前证据是否足够。
清单管理的是“为什么测、测什么、证据在哪”，测试代码仍然是可执行事实。不要把 TESTS.md 写成每个测试函数的镜像。
职责边界
| 资产 | 唯一职责 |
|---|---|
TESTS.md | 测试资产、必要测试点、缺口、状态和证据 |
| 测试代码 | 可执行输入、断言、fixture/fake 和边界模拟 |
REGRESSION.md | 模块下游、回归命令和改动后的重跑规则；只引用 TEST-ID |
| Spec/Issue | 成功标准、问题现象、影响、优先级、任务状态和排期的唯一来源 |
PROJECT_LOG.md | 只追加测试状态变化和交付结论，不复制整个清单 |
v1 由当前会话直接执行本 skill，不新增专用 agent、slash command 或强制脚本。
开始前读取
按存在性读取，不要求项目拥有全部文件：
TESTS.md与templates/TESTS.example.md。- 项目规则和地图，如
CLAUDE.md、AGENTS.md、CLAUDE_MAP.md。 - 测试目录、测试配置、CI 配置、标准测试入口和专用测试任务。
- Spec、Bug、Issue、审计、事故或回归清单；成功标准只引用，不复制进
TESTS.md。 REGRESSION.md，用于对齐模块回归命令与 TEST-ID。- 跨端接口的机器可读契约及生成/校验入口，例如 OpenAPI、JSON Schema、GraphQL schema 或 protobuf。
先识别仓库已有的测试框架和命名习惯，不强迫项目改成统一目录结构。
工作模式
1. 盘点现有测试资产
首次采用时做一次全量盘点，之后按事件增量维护：
- 找到标准测试入口，例如
pytest、npm test、make test或项目脚本。 - 扫描测试目录、配置和 CI；可以使用 collect/list 模式，但不要为了盘点执行高风险外部操作。
- 按模块、测试套件或关键流程聚合，禁止手抄每个测试函数。
- 标注层级、用途、为什么存在/保护什么风险、执行组、外部依赖、位置和当前判断。
- 将资产判断为：必要、疑似重复、缺失或疑似废弃。盘点阶段只报告，不擅自删除或重写测试。
重新盘点由事件触发，不按日历机械执行：
- 首次建立
TESTS.md：全量扫描。 - 测试目录、测试配置、CI 或标准入口变化：重扫受影响区域。
- 新增或更新 TEST-ID、Bug：增量核对相关模块。
- 重大功能、接口、业务规则或安全边界变化：重扫对应链路。
- 交付前或
/governance-sync收尾：核对本次变更涉及的条目。 - 只有测试体系整体重构或地图明显失真时，才再次全量扫描。
2. 把需求、规则和风险转成 TEST-ID
每个必要测试点使用稳定 ID，例如 TEST-ORDER-001。至少记录：
- 状态：
待补、开发中、已覆盖、不适用。 - 来源：需求、规则、风险、Bug 或事故编号。
- 模拟输入与业务预期。
- 层级与用途。
- 执行组和真实/模拟边界。
- 测试文件、测试节点和可执行命令。
纯模板、教程或历史方案中的示例编号不属于项目测试台账。确定性审计需要扫描这些文档时，可在文档顶部加 <!-- test-id-audit: examples-only --> 显式声明“本文件只有示例”；活动 Spec、Issue、Bug、评审或交付证据不得用该标记逃避登记。
来源必须链接回 Spec/Issue 中的原始成功标准。TESTS.md 只回答“哪条证据验证它”，不得另写一份可独立漂移的业务标准。成功标准含糊时，回到需求澄清能力或请项目负责人确认，不由测试 Skill 猜测。
受控层级：单元、集成、契约、E2E、冒烟。
受控用途：规则保护、关键链路、回归保护、专项保护。需要多个用途时用逗号分隔，不能临时发明新值。
不适用 必须写理由，例如风险由 schema、类型系统或 lint 更合适地机械拦截。不能用“不好测”作为理由。
3. 把 Bug 转成回归保护
修复 Bug 时，必须二选一：
- 新增或关联一个 TEST-ID；或
- 明确记录为什么只能人工验收，以及人工验收步骤和证据。
TEST-ID 应复现真实失败形状，而不是换成更容易通过的相似输入。记录修复前失败、修复后通过的证据；如果无法先运行旧代码，至少说明复现依据和未实测项。
没有 TEST-ID 或明确的人工出口，不得宣称 Bug 已完整闭环。
4. 用同一契约驱动跨端测试
前端与后端或多个服务分开开发时，把接口契约作为测试共同输入，不让各端分别手写一份接口事实：
- 找到仓库已有的机器可读契约，记录路径及可核验的版本、commit 或 hash；不把字段表复制进
TESTS.md。 - 用同一个 TEST-ID 串起四层证据：
- 契约自身：schema lint 或格式校验；
- 消费方：由契约生成或校验的类型、mock、fixture 与消费者测试；
- 提供方：对真实序列化后的响应或消息做契约校验，不能只验证内部 DTO 或类型；
- 联调：至少一条真实跨端路径；暂时没有时明确登记缺口。
- 每层记录实际命令、退出码和证据位置。生成类型或 mock 未重新生成、与契约不一致时，不得标为
已覆盖。 - 接口需要变化时先更新唯一契约源，再重新生成消费方资产并重跑提供方与联调测试。
- 仓库没有机器可验证契约时，标为
待补或不可验证，说明当前只能依赖什么证据；不能把双方各自测试为绿写成“兼容性已验证”。
契约测试证明双方是否遵守同一接口边界；E2E 继续证明真实业务路径能否工作。两者不能互相替代。
5. 审查测试证据
将状态标为 已覆盖 前，逐项确认：
- 测试文件真实存在。
- 断言验证业务行为，不只是“函数被调用”或“状态码是 200”。
- 命令可执行且退出码为 0。
- 测试进入标准 runner，或登记为命名清楚的专用执行组。
- 证据能对应 TEST-ID 的输入、预期和边界。
只看到测试文件、测试数量或绿色 CI，不足以证明必要规则已覆盖。
交付闭环还要确认：活跃 Spec/Issue 有明确成功标准；关键标准已关联 TEST-ID 或可复核的人工出口；证据确实验证预期行为；标准变化和本次重要结果已按活文档规则记入 PROJECT_LOG.md。
测试设计纪律
- 标准入口优先：先让贡献者知道“一条命令怎么跑默认测试”；慢测试、联网测试和高成本 E2E 放入命名清楚的专用组。
- 边界写清楚：E2E 要说明哪些部分真实运行、哪些外部系统被 fake/mock，以及为什么。
- 真实故障形状：Bug 回归测试使用导致事故的输入、路径和边界条件。
- 行为契约优先：断言数据之间必须满足的关系和不变量，少写只会在正常更新时报警的快照、固定枚举数量或版本字面量。
- 复用 fixture/fake：同类输入和外部边界优先复用项目已有设施，避免每个测试自造一套。
- 正反两面：关键规则至少考虑正常输入和拒绝/边界输入；权限、安全、配置传播和文件/网络路径尤其如此。
- 真实路径优先：涉及解析链、配置传播、安全边界、远程后端或文件/网络 I/O 时，应有真实导入和临时目录上的集成或 E2E 证据，不能只靠单元 mock。
- 契约单源：消费者类型/mock、提供方验证和联调测试必须引用同一契约源；禁止维护多份手写字段定义。
- 序列化边界：提供方契约测试必须检查线上实际返回形状，覆盖字段名、类型、空值、枚举、错误结构和大整数 ID 等易漂移边界。
- 规模适配：借鉴这些纪律，不复制别的大项目的并行测试基础设施或目录规模。
输出要求
创建或更新 TESTS.md 时使用 templates/TESTS.example.md 的结构，并在回复中给出：
- 标准测试入口和测试资产概况。
- 必要、缺失、疑似重复、疑似废弃的数量。
- 本轮新增或变更的 TEST-ID。
- 已实际运行的命令、退出码和未实测项。
- 下一步只列最重要的补测动作。
盘点任务默认只修改测试治理文档。除非用户另行授权，不修改生产代码、不删除测试，也不替贡献者偷偷补实现。
© qshanx, 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 skills/test-collaboration of qshanx/docs-governance.
Open the folder on GitHubat commit 520696e
Compare with similar skills
Test Collaboration 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Collaboration this skillqshanx/docs-governance | 132 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Integration E2E Testingshinpr/claude-code-workflows | 691 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Add Acceptance Testtalkincode/toughradius | 691 | — | ~827 | Automated safety check: Pass | MIT | |
| Integration E2E Testingshinpr/ai-coding-project-boilerplate | 232 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Migrate E2E To Integrationopenshift/oc-mirror | 124 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Om Integration Testsgo-musicfox/go-musicfox | 2.6k | 1 repos | ~3.6k | Automated safety check: Notes | GPL-3.0 |
Similar skills
Add Acceptance Test
talkincode/toughradius
Write CI-executable acceptance/integration tests for protocol or end-to-end changes (TR-F022).
Integration E2E Testing
shinpr/ai-coding-project-boilerplate
Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary.
Migrate E2E To Integration
openshift/oc-mirror
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Om Integration Tests
go-musicfox/go-musicfox
Run and create integration/E2E tests by exploring the live app with the configured browser provider, preserving repository-native runners, reusing the shared test environment, and diagnosing…
Patrol E2E Testing
evanca/flutter-ai-rules
A skill your agent uses when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol…
More from qshanx/docs-governance
All 10 skills in this repoAgent Entrypoints
qshanx/docs-governance
根据项目事实与已确认讨论生成、精简或审查 AGENTS.md / CLAUDE.md，明确共享规则主文件、可执行约束、PRD / Spec 读取路标和验证入口。用于项目入口只有空模板、规范含糊、双入口冲突或需要设置 Agent 项目说明时。English triggers: AGENTS.md, CLAUDE.md, project instructions, agent entrypoint…
Module Regression
qshanx/docs-governance
大项目模块间联动回归——一份 REGRESSION.md 回归台账登记"每个模块的下游消费者 + 可执行的回归验收命令"，每次改动后照台账跑回归审计，防"改一个模块悄悄弄坏其他模块"。判决靠退出码，不靠 AI 看着没问题。中文触发：模块回归、回归台账、回归审计、改A坏B、模块联动检查、影响面检查、模块牵连、下游验证、大项目改动检查。English triggers: module…
Contract First
qshanx/docs-governance
分前端/后端（或多个服务）多端开发的项目，用 CONTRACT.md 指向的唯一机器契约，各端只照它各做各的，防止字段漂移导致集成时白屏。支持单会话多 agent 和多终端各自跑两种模式。只要项目有前后端/多服务、接口字段老对不上、各端联调卡住、某端改了字段忘了通知别人、或前端为渲染一个页面要调一堆接口拼数据，就用这个…
Docs Governance
qshanx/docs-governance
作为面向长期 AI 协作项目的知识、决策与验证治理总入口，把优秀 Agent 的一次性工作沉淀为可继承、可验证、可持续演进的项目集体能力；根据用户意图把任务路由到活文档、领域上下文与 ADR、变更影响、接口契约、测试资产、模块回归或闭环设计能力，并在大型变更中组织正确顺序。用于用户只说“文档治理”“项目治理”“帮我整理项目知识”“改完怎么收尾”而未指定具体…
Living Docs Governance
qshanx/docs-governance
把长期项目的文档当成一个小系统来维护，防止文档腐烂——四份各司其职的脊柱文件（CLAUDE.md 共享章程 / CLAUDEMAP.md 地图 / PROJECTSTATUS.md 健康仪表盘 / PROJECTLOG.md 流水账）+ Codex 的 AGENTS.md 入口桥接 + 固定读序，并按需连接 ARCHITECTURE、CONTEXT、ADR、契约、测试、回归和 Issue…
Loop Design Check
qshanx/docs-governance
把一个任务"写成"一个目标导向的 loop，并"检查"这个 loop 写得对不对、会不会跑飞——防止空转烧钱 / Goodhart 作弊 / 把错的干到底。两个动作：① 写 loop（先做减法判该不该建 → 定可判定目标 → 选回路类型 → 选骨架）② 体检 loop（过五个崩法 + 可判定性 + 边界 + 降级 + judge 独立 + 判断留人红线）。中文触发：写 loop、设计…
Related
Categories
Questions about Test Collaboration
What does Test Collaboration do?
盘点并维护项目测试资产，把需求、业务规则、风险、Bug 和跨端接口契约转成 TEST-ID 与可验证证据，生成或更新 TESTS.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug…. Test Collaboration is an agent skill from qshanx/docs-governance.md。用于测试资产盘点、测试缺口分析、单元/集成/契约/E2E/冒烟分类、Bug 回归保护、前后端或多服务基于同一契约的消费者/提供者测试、测试必要性判断、测试清单维护与交付前测试证据审查。中文触发：测试盘点、测试清单、测试资产、测试缺口、测试必要性、Bug 转测试、契约测试、前后端接口测试、测试治理。English triggers: test inventory, test catalog, test gap analysis, bug-to-test, contract testing, consumer contract, provider verification, test governance.
When should I use Test Collaboration?
Test Collaboration fits situations like: tasks that involve Integration testing; tasks that involve End-to-end testing.
How do I install Test Collaboration in Claude Code?
Run `npx skills add qshanx/docs-governance --skill test-collaboration -a claude-code`. Or copy the skill folder (skills/test-collaboration in qshanx/docs-governance) into .claude/skills/test-collaboration in your project. Claude Code loads it when a task matches its description.
How do I install Test Collaboration in Codex?
Run `npx skills add qshanx/docs-governance --skill test-collaboration -a codex`. Or copy the skill folder (skills/test-collaboration in qshanx/docs-governance) into .agents/skills/test-collaboration in your project. Codex loads it when a task matches its description.
Can I use Test Collaboration 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 qshanx/docs-governance --skill test-collaboration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-collaboration, .gemini/skills/test-collaboration, .github/skills/test-collaboration and .opencode/skills/test-collaboration in your project.
What does Test Collaboration need to run?
Going by SKILL.md and its folder, Test Collaboration needs the command-line tools its instructions call (npm and make).
Does Test Collaboration access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Test Collaboration 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 Test Collaboration use?
Test Collaboration 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 Test Collaboration use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Test Collaboration?
Skills that share tags, products or a category with Test Collaboration: Integration E2E Testing (shinpr/claude-code-workflows, 691 stars), Add Acceptance Test (talkincode/toughradius, 691 stars), Integration E2E Testing (shinpr/ai-coding-project-boilerplate, 232 stars) and Migrate E2E To Integration (openshift/oc-mirror, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Collaboration?
qshanx (a GitHub user) maintains it in qshanx/docs-governance, which has 132 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 5, 2026.
Source: qshanx/docs-governance on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.