agentleFS
carverautocarverauto/serviceradar/.agents/skills/serviceradar-build-test/SKILL.md

serviceradar-build-test

Skill932 starsChanged 12 days agoApache-2.0View on GitHub

Use before building, testing, linting, formatting, producing images, or validating ServiceRadar changes locally or before a PR/release.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Prefer Bazel targets when modifying code that already has BUILD files.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

ServiceRadar Build and Test Commands

Build & Test Commands

  • Every unit test, the way CI runs them: make test — an alias for bazel test -c opt --config=remote //... --test_tag_filters=-integration_test,-acceptance_test. --config=remote, not --config=ci: the CI profile points its caches at /bazel-cache, the node volume only the BuildBuddy executors mount, so it cannot run on a workstation. Run this before opening a PR and before cutting any release. It is the only command that covers the whole repo, because the Elixir unit shards exist ONLY as bazel targets (//elixir/serviceradar_core:unit_tests_*, //elixir/web-ng:unit_tests_*) and are invisible to go test, cargo test and mix test. Two broken Elixir suites reached a release tag that way.
  • Per-language tests + Go coverage profiles: make test-toolchains (go test / cargo test / vitest / mix precommit). Useful for a fast local loop; not a substitute for make test, and make check-coverage depends on it for the cover.*.profile files.
  • Lint: make lint.
  • Focused Go packages: go test ./go/pkg/....
  • SRQL (Rust) integration tests: cd rust/srql && cargo test.
  • Bazel images: bazel run //docker/images:<target>_push. A worktree without .bazelrc.remote is not on RBE — copy the gitignored rc files first (Hard Rules).
  • First-party Wasm plugins: make build_wasm_plugins, make push_wasm_plugins, make verify_wasm_plugins. Bazel fetches the pinned TinyGo toolchain automatically; local oras is still required for publish/inspect workflows. make push_all is the container-image path; make push_all_release adds the Wasm publish/sign/verify path for release-style runs.

Prefer Bazel targets when modifying code that already has BUILD files. Always run gofmt/cargo fmt where applicable (Go formatting handled by gofmt, Rust by cargo fmt).

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.