Nativelink Bazel Verification
Testing & Qualitynativelink-bazel-verificationNativelink Bazel Verification is an Agent Skill for testing & quality published in the TraceMachina/nativelink repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when verifying NativeLink changes with Bazel, selecting focused test targets, debugging rustfmt/clippy aspect failures, or preparing a confidence report for Rust/Bazel changes.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/TraceMachina/nativelink/blob/HEAD/.claude/skills/nativelink-bazel-verification/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/nativelink-bazel-verification, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
NativeLink Bazel Verification
Use this skill when a NativeLink change needs a focused Bazel build/test plan, when CI reports a Bazel failure, or when you need to decide how much verification is enough.
Start With Scope
- Inspect the touched files and nearby
BUILD.bazelfiles. - Map changed Rust files to their crate package:
nativelink-store/for storage backends, CAS/AC, compression, Redis/S3/GCS/filesystem/memory stores.nativelink-scheduler/for action scheduling and worker matching.nativelink-worker/for local worker execution and action lifecycle.nativelink-service/for REAPI, bytestream, BEP, and worker API services.nativelink-config/for JSON5 configuration structs and examples.nativelink-util/for shared helpers.nativelink-proto/for protobuf-generated surfaces.
- Prefer focused package tests first, then broaden only when the touched surface is shared.
Common Commands
Use the repository's Bazel defaults unless the user asked for a specific Bazel version.
bazel build //:nativelink
bazel build //...
bazel test //...
bazel test //nativelink-store:memory_store_test
bazel run --config=rustfmt @rules_rust//:rustfmt
For this workspace, when the user requests Bazelisk 9.0.2:
USE_BAZEL_VERSION=9.0.2 bazelisk --output_user_root=/tmp/bazelisk-9.0.2 --batch build //:nativelink
USE_BAZEL_VERSION=9.0.2 bazelisk --output_user_root=/tmp/bazelisk-9.0.2 --batch test //...
Failure Handling
- If
rustfmtfails, run:
bazel run --config=rustfmt @rules_rust//:rustfmt
- If
clippyfails, fix the code. Don't silence lints unless the suppression is local, justified, and consistent with existing code. - If a test fails under a broad target like
//..., rerun the specific failing target with output enabled before editing. - If Bazel can't find a target, inspect
BUILD.bazelrather than guessing labels.
Verification Ladder
Use the smallest rung that proves the change:
- Single package test for narrow implementation changes.
bazel build //:nativelinkfor server-path changes.- Package-wide tests for crate-level behavior.
bazel test //...for shared crates, proto/config surfaces, toolchain changes, or release confidence.
Final Report
Always report:
- The exact commands run.
- Whether each command passed or failed.
- Any known unverified area.
- Any pre-existing dirty files that weren't part of the task.