agentleFS
Sign inStart free
DataDogDataDog/datadog-agent/.cursor/rules/bazel-buildifier.mdc

datadog-agent / rules

Cursor rule3.8k starsChanged 7 days agoApache-2.0View on GitHub

Run the buildifier test when Bazel files change

Adopted by

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

Week 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 projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 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 DataDog/datadog-agent

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

See all 56

Talked about on GitHub and Stack Overflow (56 times).

On GitHub · 48

43 more on GitHub

The file

We split this bazel-buildifier.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    When a change touches BUILD, BUILD.bazel, *.bzl, MODULE.bazel, or *.bazelrc, run:

    line 9
  2. Distinctive:

    Do not commit until the test passes.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
bazel-buildifier.mdc
---
description: Run the buildifier test when Bazel files change
globs: "**/*.bzl,**/*.bazel,**/BUILD,**/*.bazelrc"
alwaysApply: false
---

# Buildifier

When a change touches `BUILD`, `BUILD.bazel`, `*.bzl`, `MODULE.bazel`, or `*.bazelrc`, run:

```sh
bazel run //bazel/buildifier:test
```

That is the `bazel:run-buildifier-test` CI job. If it fails:

```sh
bazel run //bazel/buildifier
bazel run //bazel/buildifier:test
```

Do not commit until the test passes.

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