القائمة
Use as a thin compatibility skill when the user asks for the old mutate command; delegate to atdd-mutate for mutation testing and differential mutation workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze changed code for complex, under-tested functions using CRAP scoring; produce ranked refactor and test recommendations.
Validate strict DAE quality gates after implementation-affecting changes, require machine-readable evidence, and write the quality-gate summary before completion or release.
This skill should be used when the user asks to "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving mutants", "verify test effectiveness with mutations", "run stryker", "run mutmut", "run pitest", "set up mutation testing", "how good are my tests", "are my tests catching bugs", or mentions mutation testing, mutation score, or mutant survival in the context of testing. It adds a third validation layer to the ATDD workflow: after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies that tests actually catch bugs.
This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also available as the atdd plugin's main skill. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.
This skill should be used when the user asks to "build a feature with a team", "use ATDD with agents", "create an ATDD team", "set up a team for ATDD", "orchestrate agents for ATDD", "use team-based development", "coordinate agents for feature development", "run the ATDD workflow with teammates", "add ATDD to my team", "extend my team with ATDD", "join the team with ATDD agents", "add spec-writer and reviewer to the team", or "add ATDD roles to the existing team". It orchestrates a six-phase ATDD workflow — spec writing, spec review, pipeline generation, implementation, refine, verify & harden — spawning a fresh agent per phase so no agent erodes across a long-running feature.
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
| name | mutate |
| description | Use as a thin compatibility skill when the user asks for the old mutate command; delegate to atdd-mutate for mutation testing and differential mutation workflow. |
| arguments | [{"name":"ARGUMENTS","description":"Optional target path or flags (e.g., \"src/auth/\" to mutate only auth module)","required":false}] |
Run mutation testing on this project by following the atdd-mutate skill. This
skill exists as a Codex-native compatibility wrapper for the legacy mutate
entrypoint.
Check that both test streams are green before proceeding:
./run-acceptance-tests.sh)Detect the project language and check if a mutation tool exists in the project.
atdd-mutate skill for the 4-module
architecture (mutations, runner, core, hashing/selection) and mutation
categories.atdd-mutate skill).Configure the tool to:
generated-acceptance-tests/, acceptance-pipeline/, and specs/$ARGUMENTS is provided, scope mutations to that pathRun the mutation tool. On the custom-tool path, run dae_mutmap.py select
first and mutate only the changed functions it returns (differential
mutation testing — see the atdd-mutate skill); on the framework path,
enable the framework's incremental flag.
Report results:
dae_mutmap.py update to refresh
mutation-manifest.json; combine fresh results with cached entries for
unchanged functionsAsk whether to proceed with killing surviving mutants by using the
kill-mutants skill.