agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/aistore/cmd/ishard/AGENTS.md

aistore / ishard

AGENTS.md1.9k starsChanged 16 days agoMITView on GitHub

Apply throughout cmd/ishard/. Follow root instructions, using the module commands below. Root go test ./... and make lint-scoped exclude this separate Go module; use its Go version. For local core changes, run go work init ../.. . in cmd/ishard. Do not commit generated workspace files; remove them after verification. Read README.md for sample grouping, shard sizing, and options. Keep every sample's files together in one output shard. From the repository root (build enables dsort; lint appends it if missing): From…

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:

    Do not commit generated workspace files.

    line 8
  2. Distinctive:

    Read README.md for sample grouping, shard sizing, and options.

    line 12
  3. Distinctive:

    Keep every sample's files together in one output shard.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

iShard Agent Instructions

Apply throughout cmd/ishard/. Follow root instructions, using the module commands below. Root go test ./... and make lint-scoped exclude this separate Go module; use its Go version.

For local core changes, run go work init ../.. . in cmd/ishard. Do not commit generated workspace files; remove them after verification.

References

Read README.md for sample grouping, shard sizing, and options. Keep every sample's files together in one output shard.

Build and Verification

From the repository root (build enables dsort; lint appends it if missing):

make ishard lint-ishard

From cmd/ishard, run tests with dsort. Integration tests in ishard/ishard_test.go use config.DefaultConfig.URL (currently http://127.0.0.1:8080) and ignore AIS_ENDPOINT; deploy there per root instructions. Select a relevant test and confirm it runs.

go test -v -tags='debug dsort' -count=1 ./ishard \
  -run '^TestIshardNoRecordsSplit$'

Root integration suites exclude iShard. For shared sharding changes, also verify affected ext/dsort code with dsort.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about NVIDIA/aistore

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

See all 28

Talked about on GitHub and Bluesky (28 times).

On GitHub · 27

22 more on GitHub
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

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