bazel
Skill60 starsChanged 2 months agoMITView on GitHub
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.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- malinskibeniamin/skillstheir own version, first seen Nov 1, 2026
- gilsmt/skillstheir own version, first seen Oct 29, 2026
- Moosync/Moosynctheir own version, first seen Oct 8, 2026
- github/codeqltheir own version, first seen Nov 29, 2022
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- github/codeql★ 10ksame name
- Moosync/Moosync★ 264same name
- malinskibeniamin/skills★ 4same name
- gilsmt/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- clean-ddd-hexagonalSkill
- feature-slicingSkill
- mermaid-diagramsSkill
- modern-cssSkill
- modern-javascriptSkill
- postgres-drizzleSkill
- slack-block-kitSkill
- slack-mrkdwnSkill
- teams-adaptive-cardsSkill
- teams-message-formattingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
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
- Very specific: line 14
Use the affected targets, error output, or requested build outcome as input.
- Distinctive: line 24
If the failing target or invocation cannot be inferred, ask for it and continue independent inspection.
- Distinctive: line 29
Keep package boundaries and visibility deliberate.
- Distinctive: line 52
Use version-matched Bazel docs, ruleset release notes, and the Bazel Central Registry when bundled guidance does not establish …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 --expungeor 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.
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
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.