test-auditor

Audit test suites to classify tests as keep, revise, or remove.

3|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/prefactordev/typescript-sdk --skill test-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-auditor
Source: https://github.com/prefactordev/typescript-sdk/tree/main/.agents/skills/test-auditor
Command: npx skills add https://github.com/prefactordev/typescript-sdk --skill test-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit tests to ensure relevance, maintainability, and alignment with product goals, preventing the retention of irrelevant or misleading tests.

Core Features & Use Cases

  • Audit workflow to identify the feature or behavior under change, and to classify tests as keep, revise, or remove.
  • Keep valuable tests that protect realistic behavior; remove or revise tests that are outside scope, redundant, or misleading.
  • Provide practical guidance for improving test quality during code reviews and diff reviews.

Quick Start

Run a test-audit on the current PR to identify which tests to keep, revise, or remove, with rationale for each decision.

Frequently Asked Questions about test-auditor

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

FAQPage Schema
How do I audit tests for relevance and quality in a pull request?

To audit tests for relevance and quality, the Skill evaluates test suites against current diffs to classify tests as keep, revise, or remove. It identifies the behavior under change and flags redundant or misleading tests to ensure maintainability and alignment with product goals.

What is the best way to identify irrelevant or misleading tests in my codebase?

The best way to identify irrelevant or misleading tests is applying an audit workflow that checks coverage depth and alignment with current feature behavior. It preserves valuable tests protecting realistic behavior while providing corrective action guidance for those outside scope.

How do I clean up redundant tests during code reviews?

To clean up redundant tests during code reviews, run a test audit on the current PR to classify tests as keep, revise, or remove. This provides practical guidance for improving test quality by targeting observable outcomes and maintainability rather than implementation details.

When should I remove or revise tests in my software engineering workflow?

You should remove or revise tests when they are outside the current scope, redundant, or misleading. An audit workflow flags these tests by evaluating their coverage depth and alignment with current feature behavior across diffs, ensuring only valuable behavior-protecting tests are kept.

Does the test audit evaluate implementation details or observable outcomes?

The test audit evaluates observable outcomes and maintainability rather than implementation details. It prioritizes corrective action guidance, ensuring tests align with realistic product behavior and providing rationale for each keep, revise, or remove decision during diff reviews.