/mutate
Run mutation testing to evaluate test suite effectiveness.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/mutate
Context preview
What this command does when you run it.
Run mutation testing to evaluate test suite effectiveness.
Command definition
mutate.mdname: mutate
description: Run mutation testing to evaluate test suite effectiveness.
/mutate - Run Mutation Testing
Run mutation testing to evaluate test suite effectiveness.
Steps
1. Detect the project language and testing framework from configuration files 2. Check if a mutation testing tool is installed (Stryker for JS/TS, mutmut for Python, PITest for Java) 3. If not installed, provide installation instructions for the appropriate tool 4. Identify the source files and their corresponding test files 5. Configure mutation operators: arithmetic, conditional, string, return value mutations 6. Run the mutation testing tool on the target source files 7. Monitor progress: total mutants generated, killed, survived, timed out 8. Calculate the mutation score (killed / total * 100) 9. List survived mutants with file location, line number, and mutation description 10. For each survived mutant, identify which test should have caught it 11. Suggest specific test cases to write for the top 10 survived mutants 12. Save the mutation report to the reports directory
Rules
- Start with a single file or module to keep execution time reasonable
- Set a timeout per mutant of 10x the normal test execution time
- Exclude test files, configuration files, and generated code from mutation
- A mutation score below 80% indicates weak test coverage
- Focus on survived mutants in critical business logic first
- Do not count equivalent mutants (mutations that produce identical behavior)
- Report execution time and mutant count for performance tracking
Read more
name: mutate description: Run mutation testing to evaluate test suite effectiveness.
/mutate - Run Mutation Testing
Run mutation testing to evaluate test suite effectiveness.
Steps
1. Detect the project language and testing framework from configuration files 2. Check if a mutation testing tool is installed (Stryker for JS/TS, mutmut for Python, PITest for Java) 3. If not installed, provide installation instructions for the appropriate tool 4. Identify the source files and their corresponding test files 5. Configure mutation operators: arithmetic, conditional, string, return value mutations 6. Run the mutation testing tool on the target source files 7. Monitor progress: total mutants generated, killed, survived, timed out 8. Calculate the mutation score (killed / total * 100) 9. List survived mutants with file location, line number, and mutation description 10. For each survived mutant, identify which test should have caught it 11. Suggest specific test cases to write for the top 10 survived mutants 12. Save the mutation report to the reports directory
Rules
- Start with a single file or module to keep execution time reasonable
- Set a timeout per mutant of 10x the normal test execution time
- Exclude test files, configuration files, and generated code from mutation
- A mutation score below 80% indicates weak test coverage
- Focus on survived mutants in critical business logic first
- Do not count equivalent mutants (mutations that produce identical behavior)
- Report execution time and mutant count for performance tracking
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

