Index of every page on this site: llms.txt
All skills
ccheney avatar

/bazel

@0eea7b0
Run it yourself

Configure and troubleshoot Bazel builds. Use when editing BUILD or MODULE.bazel files, writing Starlark, diagnosing target, cache, or CI failures, or adopting or upgrading Bazel.

Use this Skill: https://skilld.dev/gh/ccheney/robust-skills/bazel

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈824 when used: this file. ≈40k more on demand in 10 files.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈186 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Bazel Monorepos

Make build changes against the actual target graph and pinned Bazel/ruleset versions. Examples cover Bazel 9.2.0; they are not an upgrade instruction. The user's explicit instructions take precedence over this skill's guidelines.

Establish the relevant context

Use the affected targets, error output, or requested build outcome as input. Check .bazelversion, relevant module declarations, BUILD files, and the configuration involved in the task. Read other repository configuration only when it affects that question.

Question Tool
Target dependencies, reverse dependencies, paths bazel query
Selected flags, platforms, toolchains, or select() branches bazel cquery with the failing invocation's configuration
Actual commands, inputs, outputs, tools bazel aquery
External modules, versions, generated repositories bazel mod
Cache misses or execution performance Execution logs, profiles, BEP

If the failing target or invocation cannot be inferred, ask for it and continue independent inspection. Do not invent repository pins or remote-cache endpoints.

Preserve the build contract

  • Declare direct inputs, dependencies, tools, and runtime data on the owning target. Use runfiles APIs for runtime resources.
  • Keep package boundaries and visibility deliberate. Neither one target per file nor one per service is a universal template.
  • For Bazel 9, use Bzlmod and explicit external language-rule loads. For older repositories, follow version-matched rules until an upgrade is requested.
  • Diagnose missing inputs or configuration differences before using clean --expunge or disabling sandboxing; those can hide the cause.
  • Validate affected targets and configurations. Reserve graph-wide builds/tests for graph-wide impact or required repository checks.

Deliver the requested patch or diagnosis with relevant target labels, evidence, and unresolved configuration dependencies. Finish checks needed for that outcome without expanding a local fix into a repository migration.

References

Load only the topic needed; use section headings within longer references.

Task Reference
Packages, labels, dependencies, visibility, BUILD style BUILD-GRAPH.md
Modules, extensions, lockfiles, overrides, WORKSPACE migration BZLMOD.md
rc files, selects, platforms, toolchains, transitions CONFIGURATION.md
Query syntax and build failure diagnosis QUERIES-DEBUGGING.md
Sandboxing, runfiles, caching, remote execution HERMETICITY-CACHING.md
CI gates, affected targets, profiles, performance CI-PERFORMANCE.md
Macros, rules, providers, aspects, repository rules STARLARK.md
Requested adoption or repository consolidation ADOPTION.md
Compact command or label lookup CHEATSHEET.md

Use version-matched Bazel docs, ruleset release notes, and the Bazel Central Registry when bundled guidance does not establish compatibility.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive and safe documentation for managing Bazel 9 monorepos, focusing on best practices for hermeticity, dependency management (Bzlmod), and performance. No security risks were identified.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 0eea7b0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
metadata
{
  "version": "9.2.0"
}

README badge

README badge for ccheney/robust-skills/bazel