Skip to main content
skill CX Codex

test-audit · fcakyon — Claude Code skill: test audits and setup

The test-audit skill reviews new and changed tests, and helps spot duplicates or low-value checks. Use it when adding tests or auditing an existing suite.

MIT ★ 1,216 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install test-audit@claude-settings
Open on GitHub

What test-audit does

Before a test is added, the skill asks what observable contract or invariant it protects, which regression would make it fail, and why current tests miss that case. Each contract should have a primary test at its strongest boundary. A second layer needs a separate transport or lifecycle risk. Checks tied to implementation details, repeated contracts, or test-only seams without production callers are candidates for rejection.

For an audit, inspect the full owners and callers, change history, and the proof that will remain before deleting a candidate. Start a whole-subsystem campaign by reading references/campaign.md; candidate criteria are in references/audit.md. After edits, run owner and sibling tests, perform required checks, and review the full diff. The audit weighs the evidence lost by a deletion, rather than aiming for a particular number of removed tests.

What it helps with

  • check which regression a new test would catch
  • find tests that repeat the same contract
  • reject checks coupled to implementation details
  • assess remaining proof before removing a test
  • review test-only seams with no production caller

Example prompts for the agent

  • Review these tests for duplicates and low-value checks.
  • Assess whether this change needs a test and what regression it should catch.
  • Audit this subsystem's tests before removing candidates.

How to install test-audit

1Plugin marketplace

/plugin marketplace add fcakyon/claude-codex-settings
/plugin install test-audit@claude-settings

This installs the whole test-audit plugin with all its skills

2Skills CLI (Vercel)

npx skills add fcakyon/claude-codex-settings --skill test-audit -a claude-code

3Manually: put the files in place

~/.claude/skills/test-audit/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/test-audit/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about test-audit

How do I install test-audit in Claude Code?

Add the marketplace with /plugin marketplace add fcakyon/claude-codex-settings, then install the skill with /plugin install test-audit@claude-settings.

What does the test-audit skill do?

It evaluates new tests and helps identify duplicate, low-value, or implementation-coupled checks. During an audit, it considers which contracts remain covered after a test is removed.

What should I read before auditing a whole subsystem?

Begin with references/campaign.md. Before removing candidates, inspect their owners and callers, history, and the proof that will remain.

Source text

SKILL.md · MIT
---
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.

© fcakyon · MIT · fcakyon/claude-codex-settings

Similar skills

All skills for Testing and QA →

test-audit by other authors comes first.

test-audit mblode test-audit — a skill for Claude Code, Cursor, Codex and other agents that removes low-value tests from a suite down to a measured target while keeping coverage. Runs as a focused directory audit or a whole-repo campaign with a numeric goal. CX Codex +1 283installs gjalla-test-audit gjalla gjalla-test-audit audits test suites to uncover false confidence, over-mocked logic, and assertions that conceal code regressions. Helpful when hardening test suites before major updates. CX Codex +1 888installs test-gap-audit official github test-gap-audit is a GitHub Copilot skill that finds gaps in test coverage and suggests specific checks. It audits the whole repository by default, or narrows the review to a named PR, feature, or code path. CX Codex +1 72installs test-driven-development Jesse Vincent The test-driven-development skill guides an agent through test-first development: verify a test fails, write the smallest passing change, then refactor. It covers features, bug fixes, and behavior changes. CX Codex +1 259,292installs momentic-test momentic-ai momentic-test is a Claude Code skill that creates and runs Momentic tests for browser, Android, and iOS apps. It works with YAML test and module files. CX Codex +1 68,600installs momentic-mobile-test momentic-ai momentic-mobile-test — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that authors and runs Momentic mobile E2E tests. Automates testing flows across Android and iOS apps. CX Codex +1 54,400installs convex-test convex Generates deterministic vitest tests for Convex backend functions using convex-test. Runs against an in-memory backend without live deployments. CX Codex +1 43,900installs

From the same set113

The whole set →
js-request-idle-callback js-request-idle-callback — a rule that moves analytics, state saving and prefetching into idle browser time so the interface stops stuttering on every click. CX Codex +1 ★ 1,216repo stars pr-comment-resolver pr-comment-resolver inspects unresolved pull request reviews, applies necessary code updates, and drafts replies for reviewers. Ideal for clearing PR feedback without manual issue hunting. CX Codex ★ 1,216repo stars list-performance-item-types list-performance-item-types is a Claude Code rule for lists with mixed layouts. It guides the agent to assign item types and keep unlike cells in separate recycling pools. CX Codex +1 ★ 1,216repo stars manage-instances manage-instances — a rule for running multiple isolated app stacks in separate worktrees, each with its own database, Redis index, and host ports. CX Codex +1 ★ 1,216repo stars webmcp-gen webmcp-gen turns a page workflow into a WebMCP tool and checks that the tool matches the behavior of the existing UI. CX Codex +1 ★ 1,216repo stars start-environment start-environment teaches the assistant how to spin up local development containers via dev docker up, wait for healthchecks, and inspect ports. CX Codex +1 ★ 1,216repo stars service-architecture The service-architecture rule maps Polar’s shared Docker infrastructure and per-worktree app stacks. Use it to understand service addresses, container dependencies, and network boundaries. CX Codex +1 ★ 1,216repo stars openship-config Inspects a repository and builds openship.json with only the overrides OpenShip needs. Use it before a first deploy or when openship config validate fails. CX Codex +1 ★ 1,216repo stars

Project sponsors

Companies that keep this analytics open