agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/migrations/openbao/AGENTS.md

nvcf / openbao

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

This native subtree packages migration scripts and independently built helper binaries. Run these commands from migrations/openbao: - Shell tests: for test in tests/*test.sh; do sh "$test" || exit; done. - Build a local image: docker buildx build --platform linux/arm64 --build-arg GIT_SHA="$(git rev-parse HEAD)" --load -t openbao-migrations:test .. - Check shell scripts with shellcheck scripts/*.sh. - Use POSIX shell and checksum-pinned source archives and builder images. - Verify embedded Go and module versions, both image architectures, numeric users, source labels, and…

The file

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

5 rules. About 0 are common, 3 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run these commands from migrations/openbao:

    line 5
  2. Very specific:

    Check shell scripts with shellcheck scripts/*.sh.

    line 9
  3. Distinctive:

    Use POSIX shell and checksum-pinned source archives and builder images.

    line 10
  4. Distinctive:

    Verify embedded Go and module versions, both image architectures, numeric users, source labels, and absence of Helm before release.

    line 11
  5. Distinctive:

    Keep the kubectl minor compatible with the supported Kubernetes versions.

    line 13

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

OpenBao migrations

This native subtree packages migration scripts and independently built helper binaries.

Run these commands from migrations/openbao:

  • Shell tests: for test in tests/*test.sh; do sh "$test" || exit; done.
  • Build a local image: docker buildx build --platform linux/arm64 --build-arg GIT_SHA="$(git rev-parse HEAD)" --load -t openbao-migrations:test ..
  • Check shell scripts with shellcheck scripts/*.sh.
  • Use POSIX shell and checksum-pinned source archives and builder images.
  • Verify embedded Go and module versions, both image architectures, numeric users, source labels, and absence of Helm before release.
  • Keep the kubectl minor compatible with the supported Kubernetes versions.
  • Record dependency/license changes in the PR. Runtime qualification also needs the consuming chart and optional migration hooks.

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.

Reviews can't be read right now.

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