ln-633-test-value-auditor

Score test usefulness by Impact × Probability and write a markdown audit.

Updated Mar 14, 2026

Search Tags:#audit #quality #code-quality #tests #software-testing #usefulness

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-633-test-value-auditor-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-633-test-value-auditor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-633-test-value-auditor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-633-test-value-auditor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and classify tests by usefulness to streamline maintenance and focus on high-value checks.

Core Features & Use Cases

Usefulness scoring: Compute Usefulness Score = Impact × Probability for every test.
Context-aware decisions: Apply business rules to adjust classifications (KEEP/REVIEW/REMOVE) based on coverage of critical flows.
Automated reporting: Produce a concise markdown audit (633-test-value.md) with per-test findings and a final score.
Workflow integration: Integrates into a coordinator pipeline to feed into planning and quality gates.

Quick Start

Run the ln-633-test-value-auditor against your project's tests to generate the 633-test-value.md audit.

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 tests for usefulness to reduce maintenance waste?▼

Test usefulness auditing calculates a score based on Impact × Probability for each test. This process contextually assesses whether a test guards a known bug or critical business rule to generate KEEP, REVIEW, or REMOVE classifications.

What is the best way to score and classify software tests by business value?▼

Scoring software tests by business value involves calculating a Usefulness Score from Impact and Probability. Context-aware decisions then apply business rules to adjust classifications for maintaining critical flow coverage.

How do I know which tests to remove or review in my codebase?▼

You can decide which tests to remove or review by evaluating their Usefulness Score and checking if they guard critical business rules. This generates clear KEEP, REVIEW, or REMOVE recommendations for each test.

Can I generate an automated markdown report for my test audit?▼

Yes, automated test auditing generates a concise markdown report. It writes per-test findings and final usefulness scores to a single file named 633-test-value.md in your output directory.

Does the test value audit integrate into a coordinator pipeline workflow?▼

Yes, the test value audit integrates into a coordinator pipeline. It feeds test usefulness findings and classifications into downstream planning and quality gates to streamline maintenance.

Why should I use usefulness scoring instead of just code coverage metrics?▼

Usefulness scoring evaluates test value by calculating Impact × Probability rather than raw execution paths. It contextually assesses whether a test guards a known bug or critical business rule to influence removal decisions.