agentleFS
Sign inStart free
ElasticKnown publisherelastic/elastic-otel-python/AGENTS.md

elastic-otel-python

AGENTS.md16 starsChanged 11 days agoApache-2.0View on GitHub

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

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

  • 2

    Very specific

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

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

    Add matching release entries to CHANGELOG.md and docs/release-notes/index.md, following each file's existing format, including release-note …

    line 4
  2. Distinctive:

    When the user specifies commits to include, list only those changes in the new release entries.

    line 5
  3. Very specific:

    Verify discussion URLs and release titles through GitHub rather than guessing discussion numbers.

    line 7
  4. Distinctive:

    Run git diff --check and review the diff to confirm the version, release entries, and requested scope agree.

    line 8

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

Release updates

  • Set the package version in src/elasticotel/distro/version.py. pyproject.toml reads this value dynamically.
  • Add matching release entries to CHANGELOG.md and docs/release-notes/index.md, following each file's existing format, including release-note anchors and linked PR references.
  • When the user specifies commits to include, list only those changes in the new release entries. Preserve earlier release entries.
  • For OpenTelemetry SDK bumps, include an Upstream changes: list linking to the release discussions in both open-telemetry/opentelemetry-python and open-telemetry/opentelemetry-python-contrib. Include intermediate releases covered by the bump, such as both 1.45.0 and 1.45.1 when upgrading from 1.44.0 to 1.45.1. Use the v1.13.0 and v1.18.0 entries as formatting examples.
  • Verify discussion URLs and release titles through GitHub rather than guessing discussion numbers. The REST discussions endpoint defaults to oldest first; use pagination or GraphQL discussions ordered by CREATED_AT descending to find recent announcements.
  • Run git diff --check and review the diff to confirm the version, release entries, and requested scope agree.

Download now (ZIP)

  • 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.

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