genotoxic

Triage mutation-testing survivors and weak-test findings into false positives, missing tests, and fuzzing targets.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill genotoxic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: genotoxic
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/genotoxic
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill genotoxic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Genotoxic turns noisy mutation-testing survivors into clear engineering actions by combining mutation results, necessist (test-statement weakness detection), and code-graph context to determine whether gaps should be fixed with stronger unit tests or with fuzzing.

Core Features & Use Cases

  • Graph-informed triage: Uses trailmark graph pre-analysis to reason about reachability, blast radius, privilege boundaries, and complexity.
  • Mutation + necessist correlation: Runs mutation testing and (optionally) necessist, then classifies findings into false positives, missing tests, fuzzing targets, or corroborated items when both tools agree.
  • Actionable reporting: Produces a structured markdown report (GENOTOXIC_REPORT.md) with bucketed findings and the mutation/necessist source for traceability.
  • Fuzzing prioritization from weak tests: Identifies functions where complex or externally reachable behavior is likely under-tested, using necessist “passed after removal” signals.

Quick Start

Read the mutation framework setup for your language, then run the full workflow by building the trailmark graph first, executing mutation testing, optionally running necessist, and finally generating the categorized GENOTOXIC_REPORT.md.

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 survivors to find missing unit tests and fuzzing targets?

Triage mutation testing survivors by running necessist and code graph analysis to classify findings into false positives, missing unit tests, and fuzzing targets. This approach categorizes survivors based on reachability, blast radius, and complexity to generate a structured markdown report.

What is the best way to avoid wasting time on equivalent mutants from mutation testing?

Avoid wasting time on equivalent mutants by using code graph analysis to filter harmless survivors. Graph-informed triage evaluates reachability and privilege boundaries to isolate false positives, directing focus toward complex or externally reachable functions that require stronger tests.

How do I identify fuzzing targets from weak test findings in my codebase?

Identify fuzzing targets from weak test findings by executing necessist to detect statements that pass after removal. Correlating these signals with mutation testing survivors highlights complex, under-tested behaviors needing fuzzing coverage.

Do I need code graph analysis to run necessist weak-test detection effectively?

You need code graph analysis to map necessist findings to production functions effectively. Trailmark graph pre-analysis provides the reachability, blast radius, and privilege-boundary context required to assign weak-test findings to actionable engineering tasks.

Can I use mutation testing and necessist correlation on a codebase with an existing green test suite?

Mutation testing and necessist correlation work specifically on codebases with an existing green test suite. This prerequisite ensures survived-mutant filtering and passing-after-removal normalization can accurately identify missing test coverage for exposed behaviors.

What limitations exist when classifying necessist findings without mutation testing results?

Without mutation testing results, necessist findings are not corroborated by both tools, reducing triage accuracy. The workflow relies on mutation and necessist correlation to distinguish missing unit tests from fuzzing targets and validate weak-test signals.