audit-tests-dev
Skill40k starsChanged 39 days agoMITView on GitHub
Invoke whenever writing, changing, reviewing, or sweeping tests.
1 other project uses a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- QuivrHQ/quivrword for word, first seen Oct 8, 2026
Who's talking about The-Vibe-Company/quivr
- Kimz“39.6k Stars:把內容串流變成可監控知識庫的開源引擎”YouTube · Oct 27, 2026 · 4 views
- @golangoss.bsky.social“quivr (⭐️ 39614) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 29, 2026 · 1 likes
- Kimerd“Turn Content Streams Into Searchable Monitored Knowledge”YouTube · Oct 27, 2026 · 1 views
- @golangoss.bsky.social“quivr (⭐️ 39585) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 14, 2026 · 1 likes
- @golangoss.bsky.social“quivr (⭐️ 39603) An open-source engine that turns continuous content streams into search and monitoring. …”Bluesky · Oct 26, 2026
The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 7
Talked about on Bluesky, YouTube and the web (7 times).
On Bluesky · 3
- Oct 29, 2026quivr (⭐️ 39614) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social1 likes and repost
- Oct 14, 2026quivr (⭐️ 39585) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social1 likes and repost
- Oct 26, 2026quivr (⭐️ 39603) An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search,… — @golangoss.bsky.social0 likes and reposts · 1 reply
On YouTube · 2
- Oct 27, 202639.6k Stars:把內容串流變成可監控知識庫的開源引擎 — Kimz4 views
- Oct 27, 2026Turn Content Streams Into Searchable Monitored Knowledge — Kimerd1 view
On the web · 2
- Oct 30, 2026The-Vibe-Company/Quivr v2.0.1 on GitHub — newreleases.io
- Sep 19, 2023The-Vibe-Company/Quivr v0.0.76 on GitHub — newreleases.io
Other versions1 project uses a version of this.
Word for word · 1
- QuivrHQ/quivr★ 40k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- quivr-search/AGENTS.mdAGENTS.md
- sdks/AGENTS.mdAGENTS.md
- armada-coordinatorSkill
- armada-runtime-claude-codeSkill
- armada-runtime-conductorSkill
- armada-runtime-herdrSkill
- armada-workerSkill
- ask-mattSkill
- better-uiSkill
- capture-learning-toolsSkill
- codebase-designSkill
- code-reviewSkill
- coordinate-fleetSkill
- design-frontend-devSkill
- diagnosing-bugsSkill
- documentation-writerSkill
- domain-modelingSkill
- emil-design-engSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- humanizerSkill
- implementSkill
- improve-codebase-architectureSkill
- mermaid-diagramsSkill
- mintlifySkill
- plan-prSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-code-devSkill
- setup-matt-pocock-skillsSkill
- ship-pr-devSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-docsSkill
- writing-for-agentsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Do not send activation reports, run tracking commands, or install hooks during this skill's execution.
- Distinctive: line 30
Before adding any test, answer four questions.
- Distinctive: line 87
Before judging a candidate, read the complete test and production owner, its entry point, callers, callees, sibling implementations, …
- Distinctive: line 90
When the test claims dependency-backed behavior, inspect the dependency source or types directly.
- Distinctive: line 95
Keep discovery read-only and report evidence before editing.
- Distinctive: line 108
Keep a test when it independently enforces a public API, plugin SDK, protocol, config, migration, storage, security, platform, default, …
- Distinctive: line 112
call ordering when order is observable behavior.
- Distinctive: line 143
Prefer net-negative production LOC.
- Distinctive: line 149
Never edit source or tests while a test runner is watching the checkout.
- Distinctive: line 153
Run the smallest owner and sibling tests with the repository's focused test command (a package, file, or name filter).
- Distinctive: line 157
Run targeted formatting, then git diff --check.
- Distinctive: line 158
Run the changed-files or full verification gate required by repository policy.
- Distinctive: line 162
After final audit edits, run the repository's code-review step.
- Distinctive: line 166
Commit, push, open a PR, or land only when authorized, through the repository's normal pull-request flow.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- skillpack:usage:start -->Skillpack runtime
Usage is observed locally by skillpack-runtime when installed through Skillpack. Package: dc27e5ca-7d73-4de4-a701-a6e513473a20@1.0.0, origin: https://skillpack.app. Do not send activation reports, run tracking commands, or install hooks during this skill's execution. Setup and updates belong to Skillpack. Continue the task when collection is unavailable. SKILLPACK_TELEMETRY=0 disables collection for this session.
<!-- skillpack:usage:end -->Test Audit
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 a plugin or core area owns); before starting one, read CAMPAIGN.md.
Authoring gate
Before adding any test, answer four questions; a missing answer means do not add it yet:
- What observable behavior, invariant, or independent contract does it protect?
- What credible regression makes it fail?
- 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.
- 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.
Then check the test against every junk pattern; a match fails the gate unless the retention bar names the contract it independently guards. A test that would break under behavior-preserving refactoring is asserting implementation, not behavior; rewrite it at the owning boundary before landing it.
Bug regression tests must fail on the pre-fix code for the intended reason and pass after the owner-boundary repair. A regression test that never demonstrably failed proves the mock, not the fix. One regression at the owner boundary covers the bug; do not replay the same scenario at every layer it crosses.
Junk patterns
The shared checklist for both modes: the authoring gate rejects a new test that matches one, and audits hunt for existing tests that do.
- assertion-free coverage probes;
- self-comparisons and identity copiers;
- copied fixtures, inventories, manifests, or export lists;
- exact source, import, or string greps;
- private predicate or call-shape tests duplicated at real boundaries;
- duplicate invocations of the same contract;
- provider-local replays of shared helpers;
- tests whose only purpose is preserving test-only exports, globals, or wrappers;
- dead production code whose only callers are tests;
- expected values produced by the helper or renderer under test;
- mocks that implement the asserted behavior, or one identical mock standing in for different APIs;
- fixtures that supply the receipt, admission, or callback ordering the owner should produce, or persistence asserted against a store the path never writes;
- capability tests that restate declared flags instead of exercising the delivery or acknowledgement the flag promises;
- negative controls that pass for an unrelated reason, such as a denial from a different guard or a rejection the production path never reaches;
- names or fixtures that promise more than the input exercises, such as a "retires the window" test asserting the window was not cleared.
Value bar
Tests justify their maintenance cost by protecting behavior, a credible regression, or an independently meaningful contract. In an audit, an existing test that must change for behavior-preserving source reorganization is suspect, not automatically deletable; the authoring gate still rejects new ones.
Before judging a candidate, read the complete test and production owner, its
entry point, callers, callees, sibling implementations, overlapping tests, CI
routing, and relevant history. Read root and scoped AGENTS.md files first.
When the test claims dependency-backed behavior, inspect the dependency source
or types directly.
Discovery
Keep discovery read-only and report evidence before editing. For broad scope, run parallel discovery lanes when available:
- core and shared packages;
- plugins, extensions, or integrations;
- UI, apps, scripts, and tooling;
- a cross-cutting pattern sweep.
Outside campaign mode, prefer a few high-confidence candidates over a large speculative inventory. Hunt for the junk patterns.
Retention bar
Keep a test when it independently enforces a public API, plugin SDK, protocol, config, migration, storage, security, platform, default, prompt-byte, generated cross-language, package, release, or architecture contract. Also keep:
- call ordering when order is observable behavior;
- regressions with a credible failure mode;
- source inspection when it is the cheapest independent guard: it fails when the contract changes (the user-facing key, byte, or path) and survives an identifier-only refactor;
- a retained test that fails on the baseline: treat it as a possible product bug, reproduce it, and repair the owner rather than deleting it.
Static or slow is not a deletion reason. A test that resembles implementation may still be the independent contract; prove otherwise before removing it.
Candidate evidence
Record every field below before editing. A missing field means the candidate is not ready for deletion:
- exact test name and location;
- what failure it can actually detect;
- non-test callers of the covered production or support seam;
- stronger remaining owner-boundary proof, or why no proof is needed;
- relevant history and the reason the test or seam exists;
- production or test-support deletion unlocked;
- risk and the focused validation command.
Edit shape
Choose one coherent owner-boundary batch. Delete obsolete test-only exports, globals, wrappers, and dead production paths instead of preserving aliases. Move retained regressions to their canonical owners. Consolidate repeated package or dependency assertions into one generic contract.
Prefer net-negative production LOC. Do not add replacement tests that restate the same implementation, and do not convert uncertain candidates into cleanup to increase deletion counts.
Validation
Never edit source or tests while a test runner is watching the checkout. Follow the repository's testing guide; route heavy proof (full suites, live stacks) through the repository's documented gates or CI.
- Run the smallest owner and sibling tests with the repository's focused test command (a package, file, or name filter).
- For removed source greps or plan assertions, run the executable script or dry-run that owns the real contract.
- Run targeted formatting, then
git diff --check. - Run the changed-files or full verification gate required by repository policy.
- Inspect
git diff --numstat; report production/tooling separately from tests and test support. - After final audit edits, run the repository's code-review step.
Landing and continuation
Commit, push, open a PR, or land only when authorized, through the
repository's normal pull-request flow. Land one
coherent PR at a time; after landing, refresh from current main and rerun
read-only discovery for the next high-confidence batch.
Handoff
Report:
- root cause and removed low-value categories;
- production owner simplifications;
- retained false positives and why they remain valuable;
- focused and full proof actually run;
- production versus test LOC;
- PR and merge state;
- named follow-ups.
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.

