mutation-testing
Skill4 starsChanged 44 days agoMITView on GitHub
通过项目已有突变测试工具审计现有测试能否发现代码逻辑错误。用户要求运行突变测试、分析存活突变体或无覆盖突变体时使用。支持 Java、Python、Go、JavaScript、TypeScript;只报告,不修改代码或测试。业务测试用例设计与场景充分性评估由 test-design 负责。
30 other projects use a version of this.
Adopted by
Most recently taken up by
- camunda/camundatheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- Integralist/agent-skillstheir own version, first seen Nov 1, 2026
- shangyiy/life-kittheir own version, first seen Nov 1, 2026
- Hakkadaikon/hymmetheir own version, first seen Oct 26, 2026
- proffesor-for-testing/agentic-qetheir own version, first seen Oct 25, 2026
Used with
Projects with it also use domain-modeling, code-review and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkilldomain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 5 projects that use this
MicrosoftSkillgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- metabase/metabase★ 50ksame name
- recharts/recharts★ 28ksame name
- camunda/camunda★ 4.4ksame name
- ThibautBaissac/rails_ai_agents★ 665same name
- proffesor-for-testing/agentic-qe★ 524same name
- s3s-project/s3s★ 315same name
- jvm-skills/jvm-skills★ 140same name
- Amplicode/spring-skills★ 126same name
- GGGODLIN/gggodlin-cc-harness★ 73same name
- Integralist/agent-skills★ 23same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-designSkill
- architecture-scoutSkill
- bug-debuggingSkill
- complexity-auditSkill
- diff-reviewSkill
- implementation-workflowSkill
- pmSkill
- prototypeSkill
- researchSkill
- test-designSkill
- wikiSkill
- worktreeSkill
The file
Files
测试有效性审计
目标
通过突变测试回答:
如果把生产代码中的一小段逻辑改错,现有测试能不能失败?
重点发现:
- 存活突变体:代码被改动后测试仍然通过
- 无覆盖代码:突变工具无法执行到相关逻辑
- 测试断言不足:测试执行了代码,但没有验证关键结果
委派
需要独立上下文时,用宿主通用子 agent 工具实际派发。传入目标项目的绝对路径、范围/基线、约束、所需技能资源的绝对路径和交付要求(资源不可读时附必要方法);子 agent 只做分配的任务,回报证据、完成状态与未验证项。仅在任务及文件/工具产物互不冲突时并行;无派发能力时自行执行并说明。
支持范围
本技能至少支持以下语言。支持的含义是:能够识别项目、选择对应的既有工具配置、限定目标范围、执行工具并统一解读报告;不负责自动安装突变测试工具。
| 语言 | 首选工具 | 适配文档 |
| Java | PIT | references/java-pitest.md |
| Python | mutmut | references/python-mutmut.md |
| Go | go-mutesting | references/go-mutesting.md |
| JavaScript | Stryker | references/javascript-stryker.md |
| TypeScript | Stryker | references/typescript-stryker.md |
如果项目已经配置了其他工具(如 cosmic-ray、gremlins),优先遵循项目现有配置,并在报告中说明实际使用的工具。
执行
- 目标按用户指定 > 指定 git 基线 > 最近改动确定;没有目标时询问,不默认全量运行。
- 识别项目已有的突变工具与配置,按语言读取上表对应 reference。只选择目标源码,排除测试和生成代码;工具无法精确过滤时说明实际范围与成本。
- 确认工具的隔离和恢复机制后执行现有配置。不要擅自安装工具或创建新配置;结束后核对并清理本次工具产生的临时源码变更和报告,保留用户已有改动。
- 重点分析
survived(测试未发现错误)与no-coverage(目标逻辑未执行)。构建、测试或工具失败应标为结果不完整,不能当作通过。
输出报告
重点报告:
- 目标范围和实际运行范围
- 识别到的语言、构建系统和突变工具
- 实际执行的命令
- 存活突变体:位置、突变类型、原始逻辑、为什么测试没有失败
- 无覆盖代码:模块、方法、建议补充的测试场景
- 工具输出是否完整
- 未解决的环境问题
边界
只报告测试漏洞和建议断言,不提交业务或测试代码修复;不为杀死突变体添加无意义断言。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

