ln-633-test-value-auditor

Compute Usefulness Scores and classify tests as KEEP, REVIEW, or REMOVE.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-633-test-value-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-633-test-value-auditor
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-633-test-value-auditor
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-633-test-value-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Risk-based value auditing for tests using Usefulness Score.

Core Features & Use Cases

  • Compute Usefulness Score = Impact × Probability
  • Classify tests as KEEP/REVIEW/REMOVE
  • Produce a structured JSON with findings

Quick Start

Run the value auditor on the current test set.

Frequently Asked Questions about ln-633-test-value-auditor

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

FAQPage Schema
How do I audit test usefulness in my CI/CD pipeline?

Test usefulness auditing computes a Usefulness Score for each test by multiplying Impact (1-5) by Probability (1-5), then classifies tests as KEEP, REVIEW, or REMOVE based on risk-based thresholds. This quantifies which tests deliver the most value in your pipeline.

What is risk-based test value auditing and when should I use it?

Risk-based test value auditing applies Impact and Probability matrices to score test effectiveness and prioritize test maintenance. Use it when you need to reduce test debt, optimize CI/CD execution time, or justify which tests to keep or remove from your suite.

How do I classify tests as KEEP, REVIEW, or REMOVE?

The auditor calculates Usefulness Score for each test, then applies configurable thresholds to automatically classify tests into KEEP (high value), REVIEW (uncertain value), or REMOVE (low value) categories based on their Impact × Probability result.

What inputs do I need to run a test value audit?

You need Impact and Probability matrices that assign scores (1-5) to each test, plus test metadata from your pipeline. The auditor produces per-test scores, classifications, and a compliance score in structured JSON output.

Can I use test value auditing for large test suites?

Yes. Risk-based test value auditing scales to any test suite size by applying uniform scoring logic across all tests. It produces findings and compliance metrics in a single JSON report regardless of suite scale.