tests-purge-unneeded

Identify tests that do not surface real bugs and justify their removal.

5|2|Updated Nov 17, 2025

Search Tags:#maintenance #ci-cd #quality-assurance #legacy-code #mutation-testing #purge-tests #test-deletion

Ready to run

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill tests-purge-unneeded

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tests-purge-unneeded
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/tests-purge-unneeded
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill tests-purge-unneeded

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tests are liabilities that pay rent by catching real bugs. Volume alone is not a quality signal; the true signal is whether removing a test would allow a real bug to reach production. This Skill helps teams identify and delete tests that fail to surface meaningful bugs, reducing maintenance cost and CI time while preserving safety.

Core Features & Use Cases

Identify and articulate the real-bug failure mode for each candidate test.
Enforce atomic commits with a one-line rationale for each deletion.
Focus on tests that guard real boundaries (I/O, error handling, security) while trimming noise.
Use cases include auditing legacy test suites, pruning after refactors, and guiding PR reviews for test reductions.

Quick Start

Identify a candidate test, articulate the failure mode it would catch, and delete it with a clear one-sentence rationale.

Frequently Asked Questions about tests-purge-unneeded

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

FAQPage Schema

How do I identify tests that are not catching real bugs in my legacy suite?▼

To identify tests not catching real bugs, articulate the specific failure mode each test guards against. If a test cannot surface a meaningful defect, it is dead-weight noise and should be removed to keep your suite lean.

When should I delete tests during a CI sweep or code refactor?▼

Delete tests during CI sweeps or refactors when the test no longer guards real boundaries like I/O, error handling, or security. Ensure deletions are atomic commits with explicit rationale to suppress noise while preserving critical coverage.

What is the best way to remove unneeded tests without losing critical coverage?▼

The best way to remove unneeded tests without losing coverage is to verify the remaining suite still exercises core paths at boundary contracts. Purge tests individually with a one-line rationale for each atomic commit.

Does mutation testing help justify test deletion in legacy codebases?▼

Mutation testing helps justify test deletion by revealing if a test actually surfaces defects. If a test fails to detect mutated code, it lacks real-bug value and can be safely purged to reduce maintenance cost.

Why does deleting low-value tests improve quality assurance outcomes?▼

Deleting low-value tests improves quality assurance by reducing maintenance cost and CI time. Volume is not a quality signal; removing tests that fail to catch real bugs ensures the suite pays rent by only guarding critical boundaries.

Can I use this test purging workflow for PR reviews on test reductions?▼

Yes, you can use this workflow to guide PR reviews for test reductions. It requires developers to articulate the real-bug failure mode for each candidate test and justify the removal with an explicit one-sentence rationale.