← ClaudeAtlas

bazel-stapler-squadlisted

Use when working with bazel, bazelisk, BUILD.bazel, gazelle, MODULE.bazel, go_deps, .bazelrc or tools/bazel in stapler-squad - building, testing, adding a Go dependency, regenerating BUILD files, or reading a Bazel failure.
tstapler/stapler-squad · ★ 1 · AI & Automation · score 64
Install: claude install-skill tstapler/stapler-squad
# Bazel in stapler-squad Bazel is the build of record (PROVISIONAL until the cutover gate). Gazelle owns Go BUILD files: run it, never hand-edit them. Every command below is a **proposal** until it is listed in `tools/bzl/verified-commands.txt` with its run log; `bash tools/bzl/check-skill-proposals.sh` fails CI on an unlisted, unmarked command. Replace proposals with verified output before the PR merges. ## Commands | Intent | Command | |---|---| | Build the binary | `make build` (wrapper over `bazel build //:stapler-squad`) <!-- proposal --> | | Test one package | `bazel test //session:session_test --test_output=errors` <!-- proposal --> | | Test one test by name | `bazel test //session:session_test --test_filter=TestFoo --test_output=errors` <!-- proposal --> | | Regenerate BUILD files | `make gazelle` <!-- proposal --> | | Check BUILD files are fresh | `make gazelle-check` <!-- proposal --> | | Plain go / gopls need generated code | `make sync` <!-- proposal --> | | Host health, first thing when something looks wrong | `make bazel-doctor` <!-- proposal --> | | Why is it slow | the `bazel-perf` skill (`--profile`, critical path) | Targets follow Gazelle naming (`//session:session`, `//session:session_test`); do not override it. Always go through `tools/bazel` (Bazelisk runs it automatically; direct calls need `BAZEL_REAL`). It queues for one of N host-wide slots, runs Bazel in a memory-capped scope and, for agents, adds `--config=agent` (quiet, no ANSI, capped failure