genotoxic

Analyze mutation testing results using code graph analysis to categorize survived mutants.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill genotoxic-manuelbrandner85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: genotoxic
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.agents/skills/genotoxic
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill genotoxic-manuelbrandner85

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires trailmark, necessist, and includes references (resource) components.

What problem does it solve?

This Skill solves the problem of noisy, overwhelming mutation testing results by using code graph analysis to filter out harmless mutants and prioritize actionable test improvements.

Core Features & Use Cases

  • Graph-Informed Triage: Uses code complexity, entrypoint reachability, and blast radius to categorize survived mutants.
  • Necessist Integration: Identifies weak test assertions by removing test statements and verifying if tests still pass.
  • Actionable Reporting: Automatically generates a report categorizing findings into false positives, missing test coverage, and high-value fuzzing targets.

Quick Start

Use the genotoxic skill to analyze the current directory and generate a triage report for all survived mutants.

Frequently Asked Questions about genotoxic

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

FAQPage Schema
How do I triage mutation testing results effectively?

Triage mutation testing results by using graph analysis to filter harmless mutants and prioritize actionable test improvements. This approach categorizes survived mutants based on code complexity, entrypoint reachability, and blast radius.

What is the best way to identify false positives in mutation testing?

Identify false positives in mutation testing by analyzing the blast radius and entrypoint reachability of survived mutants. Graph-informed triage automatically filters out harmless mutants that do not impact critical code paths.

How do I find missing test coverage and fuzzing targets?

Find missing test coverage and high-value fuzzing targets by analyzing survived mutants with code graph data. The analysis categorizes findings into missing assertions and areas suitable for targeted fuzzing.

Do I need trailmark and necessist installed to analyze survived mutants?

Yes, you need trailmark and necessist installed and configured for the target language. Trailmark computes blast radius and reachability, while necessist identifies weak assertions by removing test statements.

How does necessist integration work for weak test assertions?

Necessist integration works by removing test statements and verifying if the tests still pass. This process identifies weak assertions and missing test coverage, which are then categorized in an actionable report.

Can I use graph-informed triage for any programming language?

Graph-informed triage supports any programming language where mutation testing frameworks, trailmark, and necessist are installed and configured. The tool analyzes the codebase to compute reachability for survived mutants.