n-coverage-fix

Automate surviving mutant identification and iterative test generation in git worktrees.

Updated Jun 2, 2026

Search Tags:#automation #testing #refactoring #coverage #mutation-testing #stryker

Ready to run

npx skills add https://github.com/vitaliytv/7n --skill n-coverage-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: n-coverage-fix
Source: https://github.com/vitaliytv/7n/tree/main/.cursor/skills/n-coverage-fix
Command: npx skills add https://github.com/vitaliytv/7n --skill n-coverage-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @nitra/cursor.

What problem does it solve?

This skill addresses the manual burden of increasing mutation testing scores by automatically identifying surviving mutants and iteratively generating the necessary tests to cover them.

Core Features & Use Cases

Automated Mutation Analysis: Runs coverage reports and isolates surviving mutants into a compact index for efficient processing.
Iterative Test Generation: Automatically triggers agents to write tests for specific code slices, repeating the process until mutation score convergence is reached.
Use Case: When a project has a low mutation score, use this skill to systematically identify and eliminate dead code or untested logic without manually parsing large coverage reports.

Quick Start

Run the n-coverage-fix skill in the root of your project to automatically identify and write tests for all surviving mutants.

Frequently Asked Questions about n-coverage-fix

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

FAQPage Schema

How do I automatically generate tests to kill surviving mutation testing mutants?▼

Automated mutation test generation identifies surviving mutants and iteratively writes tests to cover them. This process runs within isolated git worktrees to ensure safe execution until mutation score convergence is reached.

How does automated mutation analysis handle test generation for untested logic?▼

Automated mutation analysis runs coverage reports and isolates surviving mutants into a compact index. It then triggers agents to iteratively write tests for specific code slices, eliminating untested logic without manual report parsing.

Do I need @nitra/cursor to run mutation score convergence and coverage analysis?▼

Yes, achieving mutation score convergence requires integration with the @nitra/cursor CLI. The skill operates alongside this CLI and standard test runners to automate coverage analysis and test suite updates.

Can I run parallelized test generation with isolated git worktrees for mutation testing?▼

No, mutation testing execution is intentionally non-parallelized within isolated git worktrees. This ensures safe, sequential test generation and coverage analysis without conflicting worktree operations.

What is the best way to increase mutation testing scores without manually parsing coverage reports?▼

The best way to increase mutation testing scores is automating the identification of surviving mutants. This systematically targets dead code and untested logic, generating tests iteratively instead of parsing large reports manually.

Why does my mutation testing score stay low after adding standard coverage tests?▼

Mutation testing scores remain low because standard coverage does not verify logic correctness. This skill addresses the issue by automatically identifying surviving mutants and generating targeted tests to kill them.