agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/deploy/releases/AGENTS.md

nvcf / releases

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

Each X.Y.Z/ directory contains the umbrella product manifest.json and customer-facing notes.md. Follow docs/dev/umbrella-releases.md from the repository root. Released manifests, tags, and assets are immutable. Select exact released stack tags and original inventories. Do not copy stack directories from a candidate branch or merge that branch wholesale into main. The manifest source commit supplies provenance, LICENSE, and NOTICE; it must be an ancestor of the final publication target on main. Build the release tool from the repository root: Validate the manifest…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Use umbrella publish without --write to validate committed metadata and notes before publication.

    line 20
  2. Distinctive:

    Run git diff --check before committing.

    line 22
  3. Distinctive:

    Use generated JSON and concise ASCII Markdown.

    line 25

≈ “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

Product release metadata

Each X.Y.Z/ directory contains the umbrella product manifest.json and customer-facing notes.md. Follow docs/dev/umbrella-releases.md from the repository root. Released manifests, tags, and assets are immutable.

Select exact released stack tags and original inventories. Do not copy stack directories from a candidate branch or merge that branch wholesale into main. The manifest source commit supplies provenance, LICENSE, and NOTICE; it must be an ancestor of the final publication target on main.

Build the release tool from the repository root:

go build -C tools/docs-version-sync -o /tmp/nvcf-docs-version-sync .

Validate the manifest and selected inventories with umbrella check, assemble with umbrella bundle, and verify the result with umbrella verify-bundle. Use umbrella publish without --write to validate committed metadata and notes before publication. See the release guide for the required arguments. Run git diff --check before committing. These checks validate packaging; the release owner records qualification of the selected runtime combination.

Use generated JSON and concise ASCII Markdown. Link customer notes to stable source commits when the matching maintained documentation is not yet active.

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