- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add dzhng/skills --skill audit-tests -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add dzhng/skills --skill audit-tests -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add dzhng/skills --skill audit-tests -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add dzhng/skills --skill audit-tests -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/dzhng/skills/tree/HEAD/skills/engineering/audit-testsDe l'éditeur
Audit independent proof: what bug would escape if this test disappeared? The result is a map of contracts to their surviving tests, with evidence for what to keep, repair, combine, or remove. Fewer tests is not the objective; less maintenance for the same or better confidence is.
write-tests owns how to write and falsify a test. This skill owns whether that test adds proof and where that proof belongs. review owns closing out the resulting changes.
For each candidate, record its location and name, actual detectable failure, reason for existing, production consumers of any supporting hook, and decision:
Include the supporting source/history evidence, cleanup unlocked, risk, and validation command. Missing evidence stays an open question, not a deletion.
Use these as investigation prompts, not automatic removal rules:
Behavior includes compatibility and operational contracts: API and SDK shape, wire bytes, prompts, defaults, configuration, migrations, storage, security, platform behavior, generated cross-language agreement, package contents, release rules, and architectural boundaries. A static assertion can be their cheapest independent proof. Observable ordering also belongs here.
Ask whether the test survives an internal rename while detecting a broken external promise. Exact bytes may be essential to a protocol; exact private identifiers usually are not. Neither slowness nor resemblance to implementation is sufficient evidence for deletion. Do not add refactor-sensitive coverage when the real contract can be exercised directly.
An existing failure may be a product defect. Reproduce and investigate it; never remove a valid claim to make the audit green. Repair in-scope defects separately, with a failing control and passing fix on the same harness. Record unrelated defects as follow-ups and keep their coverage.
Scale the accounting before scaling the edits:
Hand off the contract map, decisions and reasons, production simplifications, valuable tests deliberately retained, preservation gaps and their resolution, and verification actually run. For broad sweeps, include before/after size for production, tests, and support separately, plus remaining batches and integration state. Size describes the outcome; it never sets the deletion target. Claim a complete subsystem audit only when the inventory has no unexamined entries.
Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the
---name: audit-testsdescription: Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant…---# skills/engineering/audit-tests/SKILL.mdVue d'ensemble
Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.
FAQ
Téléchargez skills/engineering/audit-tests/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/dzhng/skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.