bazel-evidence-engineeringlisted

# Bazel Evidence Engineering Use Bazel to answer the engineering question with the smallest sufficient evidence, then widen only when dependency impact, risk, or a named acceptance gate justifies it. This skill guides decisions. It does not expand authorization, convert inspection into mutation, or make publication, deployment, signing, remote upload, or another external effect implicit. Preserve unrelated work and distinguish moving snapshots from frozen conclusions. Current compatibility guidance was reviewed against Bazel 9.2.0. Repository pins remain authoritative for version-sensitive work. ## Confirm that Bazel owns the question Use this skill when Bazel controls the relevant surface or when the task explicitly evaluates adopting Bazel for it. A repository may use Bazel for only part of its build, test, package, or release flow; identify the real authority before treating Bazel as formal acceptance. Stay out of unrelated build systems, prose-only work, and runtime-only incidents. Bring Bazel back only for an owning target, a build/configuration hypothesis, or formal regression evidence. ## Start with repository truth when it matters Before repository-specific analysis or execution, inspect the checked-in Bazel and ruleset pins, governing instructions, effective rc/wrapper configuration, relevant targets, and authorization identity. Repository facts outrank examples in this skill. Read [repository-first-inspection.md](references/repository-first-inspection.md) w