test-audit
Skill0 starsChanged 34 days agoApache-2.0View on GitHub
Use when adding or changing tests, reviewing their value, or auditing a suite for tautologies, redundant coverage, brittle assertions, and unused test support. Requires evidence for every removal and preserves distinct regression protection.
83 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- coder/codertheir own version, first seen Nov 15, 2026
- smarzban/agent-skillstheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- kontourai/stationtheir own version, first seen Nov 14, 2026
- iliaal/ai-skillstheir own version, first seen Nov 14, 2026
- 851-labs/codevisortheir own version, first seen Nov 13, 2026
Used with
Projects with it also use chips, redo and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
udecodeSkillchips
Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.
Also in 3 projects that use this
Scylla23Skillredo
Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.
Also in 3 projects that use this
Aetheria-Labs1Skillplan-page
Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.
Also in 3 projects that use this
SocialKit-APISkillvideo-transcripts
Extract transcripts from social videos through SocialKit across YouTube, TikTok, Instagram, Facebook, X/Twitter, LinkedIn, and direct video file URLs. Use when the user asks to transcribe, get captions or subtitles, pull the spoken text, or read what a video says, including one video or many at once. Returns full text plus timestamped segments. Not for posting, private accounts, or unrelated website scraping.
Also in 3 projects that use this
clawdbotSkillpr-simplify
Simplify your own change to its smallest complete fix. Use before opening a PR, before pushing large repairs to one, or when asked to shrink a PR or clean up slop.
Also in 3 projects that use this
spitoglouSkilltechnical-documentation
Create and improve technical documentation including architecture designs, PRDs, API docs, code explanations, and visual diagrams. Use when asked to document systems, explain codebases, create design documents, write PRDs, generate Mermaid/PlantUML diagrams, review architecture, write user stories, or create pull request descriptions. Triggers include "document this", "create a design doc", "explain this code", "write a PRD", "create a diagram", "architecture overview", "user story for", "PR description".
Also in 3 projects that use this
Other versions83 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- dvmkit/dvmctl★ 099% same
Wrote their own version · 82
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- garrytan/gstack★ 142ksame name
- paperclipai/paperclip★ 114ksame name
- simstudioai/sim★ 30ksame name
72 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- public-readmeSkill
- dvmSkill
The file
Files
Test value
Apply repository verification and ownership rules first. Tests protect behavior or an independent contract; counts and coverage percentages do not establish that protection.
Before writing a test
Identify the behavior, a plausible defect, and why existing tests miss it. Choose the cheapest boundary that exposes that defect. A second layer needs a distinct failure to catch. Mock external inputs, not the behavior being asserted. Prefer extending existing cases when they own the same contract.
Expected results must come from a specification, independently derived example, or meaningful property. Fixture self-checks, configured mock output, self-comparisons, and expected values computed by the same implementation do not qualify. Determinism, round trips, idempotence and retry/replay are valid when a production defect can violate the property.
For a bug fix, demonstrate that the test fails for the intended reason without the fix, then passes with it. If that control cannot run, state the missing evidence. Avoid production exports, switches, or indirection used only to reach implementation details; first seek an existing observable boundary.
Audit an existing suite
- Set the boundary. Pin the baseline revision. Inventory owned test files, support code, generated tests and CI routing. Name which files receive a full semantic review and which receive only candidate searches. Record baseline test results and existing failures separately. Use available coverage tooling as supporting evidence; do not install a coverage or mutation framework merely for cleanup.
- Read before judging. Read candidate tests including tables, their production owner, callers and relevant history. Identify what each assertion actually detects. Look for vacuous negatives, fixtures doing the work, assertions weaker than their names, repeated proof at multiple layers, and source-spelling checks. These are candidates, not automatic deletions.
- Record decisions. For each declaration in the fully reviewed group, mark retain, repair, consolidate or delete, with a short reason. For each proposed removal/repair, record location, credible defect, remaining proof or absence of a meaningful contract, history, affected support code and focused validation. Group repetitive retained cases only when they share the same reasoning; account for distinct table rows.
- Compare layers. Name the retained suite for each contract before editing. Move unique assertions into it before retiring duplicates. Remove support or production access points only after checking all callers and supported API obligations. Similar syntax or a slower test does not prove redundancy.
- Apply a coherent batch. Preserve separate money, recovery, lifecycle, package/release, security and architecture protection. Source inspection can be appropriate when a source property is itself the contract; check a deliberately invalid example. Treat failing baseline tests as possible product defects, never cleanup opportunities. Keep substantial unrelated fixes separate.
- Verify preservation. Run affected retained tests and required repository gates after edits. Use a deliberate defect or invalid input to show changed protection fails for the intended reason; restore any temporary source change exactly before continuing. Do not edit a checkout during its test run. Have an independent reviewer compare removed assertions with retained proof and resolve gaps before landing.
Keep a compact audit record with scope, decisions, evidence, baseline/final test and support size, separately counted production changes, actual checks and skips. Rerun discovery when upstream changes the audited owner. No deletion target, weaker gate, increased timeout, or acceptable coverage drop authorizes losing a distinct contract. A justified retention is a completed audit decision.
Comments and scope
Do not add tests solely for prose or policy wording. Preserve useful rationale, API semantics, functional annotations and tooling directives while removing comment noise. Tests do not justify otherwise dead production paths. Follow normal review, delivery and CI ownership rules; this skill grants no publication or permission changes.
Method informed by OpenClaw's test-audit skill, adapted to local verification and test-ownership rules.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

