agentleFS
DataDogDataDog/dd-trace-java/buildSrc/AGENTS.md

dd-trace-java / buildSrc

AGENTS.md739 starsChanged 6 days agoApache-2.0View on GitHub

Use gradle-best-practices before changing Gradle code here. If it is missing or incomplete, follow the skill setup before editing. For new conventions, follow the build logic placement advice. The Java 8 target in build.gradle.kts is needed by build-time instrumentation and Muzzle workers. A newer Gradle daemon or compiler JVM does not remove that requirement. JMH uses the consuming build's plugin classpath. Read the comments in its convention before changing that integration or adding JMH to implementation. The plugin tests use…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Use gradle-best-practices before changing Gradle code here.

    line 3
  2. Very specific:

    Keep the :test selector when filtering so the filter does not reach unrelated subprojects.

    line 20

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

Working in buildSrc

Use gradle-best-practices before changing Gradle code here. If it is missing or incomplete, follow the skill setup before editing.

For new conventions, follow the build logic placement advice.

The Java 8 target in build.gradle.kts is needed by build-time instrumentation and Muzzle workers. A newer Gradle daemon or compiler JVM does not remove that requirement.

JMH uses the consuming build's plugin classpath. Read the comments in its convention before changing that integration or adding JMH to implementation.

Tests

The plugin tests use JUnit 5 and Kotlin. Reuse GradleFixture for TestKit tests. CLI tests need -PrunBuildSrcTests; see the test commands. Keep the :test selector when filtering so the filter does not reach unrelated subprojects.

Changes to call-site-instrumentation-plugin or modifiable-config-agent also need their own subproject tests. Run ./gradlew -p buildSrc spotlessCheck for formatting.

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.