# Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests in the eve repository.

- Repository: https://github.com/vercel/eve (5761 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

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

## Description

Invoke whenever writing, changing, reviewing, or sweeping tests in the eve repository. Authoring gate for new tests plus audit workflow for low-value, slow, implementation-coupled, or duplicative tests and the test-only production seams they demand.

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

# Test audit

Adapted from the OpenClaw
[`test-audit`](https://github.com/openclaw/openclaw/blob/main/.agents/skills/test-audit/SKILL.md)
skill for eve's test tiers and tooling.

Three modes, one value bar. Authoring mode gates every new or changed test at
write time. Audit mode runs focused sweeps of tests that re-assert source,
duplicate stronger proof, couple behavior to implementation, or keep test-only
production seams alive. Continue broad audits as separate coherent follow-up
PRs; optimize for confidence, not deletion count. Campaign mode prunes one
whole subsystem's test surface (every test file one core area or package
owns); before starting one, read [CAMPAIGN.md](CAMPAIGN.md).

Read the root [`AGENTS.md`](../../../AGENTS.md) testing section first. It
defines eve's four tiers (unit, integration, scenario, e2e); a test belongs in
the tightest tier that can express its assertion.

## Authoring gate

Before adding any test, answer four questions; a missing answer means do not
add it yet:

1. What observable behavior, invariant, or independent contract does it protect?
2. What credible regression makes it fail?
3. Why does existing coverage not already catch that failure? Each contract has
   one primary test owner at the strongest boundary; another layer needs its
   own distinct risk, such as a transport or lifecycle failure the owner cannot
   reach. Prefer extending a table-driven case or shared fixture over a
   near-duplicate test; consolidate duplicated setup in the same change.
4. Does it need a production seam (export, flag, wrapper, injection hook) that no
   production caller needs? If yes, move the test to the real boundary instead.

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