agentleFS
Sign inStart free
QuivrHQQuivrHQ/quivr/quivr-search/AGENTS.md

quivr / quivr-search

AGENTS.md40k starsChanged 37 days agoMITView on GitHub

Follow the testing standard before changing tests.

1 other project uses a version of this.

Trending

Quiet since September.about the whole repository

Dec 2025: 0 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 3 mentionsJun 2026: 0 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the QuivrHQ/quivr repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about QuivrHQ/quivr

The biggest 5 of 67 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 67

Talked about on GitHub, Bluesky and YouTube (67 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 12

7 more on Bluesky

On YouTube · 5

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the testing standard before changing tests.

    line 3
  2. Distinctive:

    Use independent literal period bounds and distinct day identities.

    line 6
  3. Distinctive:

    Check concurrency and batch caps as upper bounds, with complete work coverage.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Demo test ownership

Follow the testing standard before changing tests.

  • Facet rules belong in tests/explore.test.mjs through createExplorer().facets; supply raw engine answers and literal corpus schemas at its upstream boundary. Keep date/count helpers private.
  • Use independent literal period bounds and distinct day identities. Compare complete outgoing predicates because bucket fixtures do not evaluate filters.
  • Check concurrency and batch caps as upper bounds, with complete work coverage; a smaller legal batch must pass.
  • Browser fixtures prove client rendering and interaction; facade tests prove transport and scope. Keep separate literal arithmetic owners when fixtures reuse production helpers.
  • Name the assertions observed: published aggregates do not identify one write, and screenshots do not prove internal layout fit.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free