fcakyon/claude-codex-settings / plugins/test-audit/skills/test-audit
test-audit
VerifiedThis skill should be used when the user asks to "write a test", "review these tests", "audit tests", "prune low-value tests", or "find duplicate tests", and whenever writing, changing, reviewing, or sweeping tests. Gates new tests and audits low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 2.8 KB |
| references/audit.md | markdown | 3.3 KB |
| references/campaign.md | markdown | 5.4 KB |
SKILL.md
View on GitHub---
name: test-audit
description: This skill should be used when the user asks to "write a test", "review these tests", "audit tests", "prune low-value tests", or "find duplicate tests", and whenever writing, changing, reviewing, or sweeping tests. Gates new tests and audits low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand.
---
# Test Audit
- Authoring gates every new/changed test.
- Audits: remove low-value proof in coherent owner batches; never chase deletion counts.
- Whole-subsystem campaign: read [references/campaign.md](references/campaign.md) first.
## Authoring gate
Before adding test, answer:
1. Protected observable behavior, invariant, or independent contract?
2. Credible regression that makes it fail?
3. Why existing proof misses it? Each contract: one primary owner at strongest
boundary. Another layer needs distinct transport/lifecycle risk. Extend
tables/shared fixtures; consolidate repeated setup.
4. Export, flag, wrapper, injection hook with no production caller needed?
Move proof to real boundary instead.
- Use the repository testing guide for boundary and cost decisions.
- Regressions must fail pre-fix for intended reason, pass after repair; report
unavailable baseline proof.
- One owner regression covers bug; never replay at every crossed layer.
- Behavior-preserving refactors should not break test.
## Junk patterns
- Reject self-comparisons, copied inventories, source greps,
implementation/call-shape assertions, duplicate contracts, test-only seams,
subject-generated expected values, mocks supplying asserted behavior.
- Fixtures must not fabricate owner receipts/order or claim persistence path
never writes.
- Negative controls must fail at intended guard; names must match exercised behavior.
- Auditing candidates: use [full checklist](references/audit.md#junk-patterns).
## Retention bar
- Keep independent API, SDK, protocol, config, migration, storage, security,
platform, default, prompt-byte, generated-language, package, release,
architecture, observable-ordering contracts. Static/slow ≠ disposable.
- Source inspection must survive identifier-only refactors and guard independent
user-facing contract.
- Baseline failures may be bugs to repair, not tests to delete.
## Audit and validation
- Before audit edit: read [candidate evidence and workflow](references/audit.md#candidate-evidence);
inspect full owners/callers/history; record remaining proof before deletion.
- Delete obsolete production seams with tests; never optimize for deletion counts.
- Follow the repository testing guide; preserve active test checkouts;
run owner and sibling tests plus required checks, then review the full diff.
- Report causes, retained contracts, proof/cost, production versus test LOC,
follow-ups. Commit/push/land only with task authority.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |