mutation-test

Run language-dispatched mutation testing and generate dated per-project reports.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill mutation-test-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mutation-test
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/mutation-test
Command: npx skills add https://github.com/AAbdulghany/fms --skill mutation-test-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mutation testing reveals whether a test suite truly constrains behaviour by detecting mutants that tests fail to catch, going beyond standard code-coverage metrics.

Core Features & Use Cases

  • Language-dispatched mutation testing across TypeScript/JavaScript, Python, Go, and Ruby using dedicated runners (Stryker, MutPy, go-mutesting, and Mutant).
  • Milestone-bound and on-demand audits that produce a dated mutation report stored at projects/<name>/quality/mutation-YYYY-MM-DD.md, with a six-section report including trend data and top-5 survivors.
  • Graceful degradation when no mutation tester is installed, with install advisory and a --check-only mode that reports readiness without executing tests.

Quick Start

Run /mutation-test on a project to assess test strength across languages.

Frequently Asked Questions about mutation-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run mutation testing to check if my tests actually catch code defects?

You can run cross-language mutation testing directly on your project to measure test strength. The Skill detects the project language and dispatches the appropriate mutation tester to uncover behavioural gaps missed by standard coverage.

Can I use mutation testing across TypeScript, Python, Go, and Ruby projects?

Yes, language-dispatched mutation testing supports TypeScript and JavaScript via Stryker, Python via MutPy, Go via go-mutesting, and Ruby via Mutant. The Skill detects the language and applies the correct runner automatically.

What do I need installed before running a mutation test audit?

You need the relevant mutation testers installed for your project's language. If none are present, the Skill gracefully degrades by issuing an install advisory and exit code 3, or you can run --check-only to report readiness.

How does mutation testing compare to standard code coverage?

Standard code coverage only checks if lines execute, while mutation testing verifies that tests truly constrain behaviour by introducing faults. This reveals whether your tests actually detect logic errors beyond just hitting lines.

How are mutation testing results reported and tracked over time?

Mutation testing results are saved as a dated report at projects/<name>/quality/mutation-YYYY-MM-DD.md. The six-section report includes trend data and highlights the top-5 surviving mutants to track test quality over time.

When should I run mutation testing during a project lifecycle?

Mutation testing is designed to run at milestone boundaries and on-demand. This ensures you assess test strength at critical project phases rather than continuously, balancing audit depth with execution overhead.