test-strength

Audit code coverage and mutation analysis on changed files.

2|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bigeasyfreeman/adlc --skill test-strength
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-strength
Source: https://github.com/bigeasyfreeman/adlc/tree/main/skills/test-strength
Command: npx skills add https://github.com/bigeasyfreeman/adlc --skill test-strength

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, mutmut, stryker, cargo-mutants, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures that test strength is adequate by auditing test coverage and mutation analysis on changed files, providing insight into the effectiveness of the test suite.

Core Features & Use Cases

  • Coverage and Mutation Analysis: Evaluates test suite coverage and mutation analysis to determine test effectiveness.
  • Language Support: Detects the dominant repository language and uses standard mutation tools accordingly.
  • Audit Workflow: Executes a comprehensive workflow to generate a report on test strength, including coverage metrics and mutant classifications.
  • Gate Thresholds: Applies coverage and mutation survival thresholds to determine the test suite's strength.
  • Output Report: Produces a JSON report detailing the results of the audit.

Quick Start

Run the 'test-strength' skill to audit the test strength on changed files after 'qa' passes and before 'slop_gate'.

Frequently Asked Questions about test-strength

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

FAQPage Schema
How do I run mutation analysis on changed files in my repository?

Mutation analysis on changed files is performed by auditing code coverage and applying mutation tools to gauge test suite strength. The skill detects the dominant repository language and executes the appropriate mutation tool to evaluate test effectiveness.

What is mutation analysis and how does it measure test suite strength?

Mutation analysis measures test suite strength by injecting faults into code and verifying if tests catch them. Combined with code coverage auditing, it evaluates whether tests effectively detect changes, classifying surviving mutants to judge survivor materiality.

Do I need git and mutation tools installed to audit test strength?

Yes, auditing test strength requires git to identify changed files and mutation analysis tools based on the detected language. The skill detects the dominant language and employs standard mutation tools accordingly to execute the audit workflow.

Does mutation testing work with Python and Rust projects?

Mutation testing works with multiple languages by detecting the dominant repository language and using standard mutation tools accordingly. The skill supports mutation analysis for projects compatible with mutmut and cargo-mutants, adapting to the detected language.

What's the best way to enforce test strength thresholds before merging code?

The best way to enforce test strength is applying coverage and mutation survival thresholds to determine test suite strength. The skill audits changed files, applies gate thresholds, and produces a JSON report detailing audit results for evaluation.

Why does test coverage pass but mutation analysis shows surviving mutants?

Test coverage passing while mutation analysis shows surviving mutants indicates tests execute code without adequately asserting behavior. The audit workflow classifies mutants and applies survival thresholds to judge survivor materiality and determine actual test suite strength.