# Prune Test Suite

Removes redundant or vacuous tests while keeping useful regression coverage.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill test-audit -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill test-audit -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill test-audit -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill test-audit -g -a gemini-cli -y`

## Description

Garden the test suite by finding and removing redundant, vacuous, or implementation-coupled tests while preserving useful regression coverage. Use for test audits, test pruning, duplicate coverage, or reducing CI test cost. Supports focused cleanups and coordinated audit campaigns.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Test Audit

Reduce execution and maintenance cost while preserving meaningful failure
detection. Investigate aggressively; delete only with evidence. Retaining an
area after review is a valid result. This skill is self-contained; upstream
attribution is in [NOTICE.md](NOTICE.md).

## Choose the scope

- Focused cleanup: follow this entry point and read the
  [candidate evidence guide](references/audit.md) before editing.
- Multiple owners, agents, or PRs: also read [CAMPAIGN.md](CAMPAIGN.md). Declare
  whether the work is a targeted sweep or an exhaustive subsystem audit.
- Validation and cost claims: read [references/validation.md](references/validation.md).
- Paperclip commands, invariants, and delivery: read
  [references/paperclip.md](references/paperclip.md) alongside repository instructions.

## Decision gate

For every proposed removal, answer:

1. Which observable contract and plausible regression do the assertions cover?
2. Which retained file/case detects that regression through the responsible
   production code? Otherwise, why is the assertion vacuous or contract retired?
3. Does this candidate uniquely cover a transport, permission, lifecycle,
   storage boundary, platform, default, or other independent failure mode?
4. What improves: executions, fixtures, processes, maintenance, or runtime?

Prefer the smallest test that reaches the code responsible for the contract.
A broader suite is not automatically stronger proof. Similarity, size, slowness,
or suspected AI authorship alone never justify deletion.

## Prevent new duplication

Apply this gate to tests added or changed during gardening:

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/test-audit/SKILL.md