vendor
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Apollo-Lite Bazel Bzlmod vendor workflow for preparing and validating offline source deliveries.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- buildSkill
- change-reviewSkill
- container-buildSkill
- engineering-solution-designSkill
- interface-migrationSkill
- issue-localizationSkill
- lintSkill
- long-horizon-developmentSkill
- model-artifact-integrationSkill
- multi-repo-devSkill
- performance-optimizationSkill
- repository-agent-setupSkill
- simulation-regressionSkill
- test-impact-analysisSkill
- unified-core-runtimeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this when preparing an Apollo-Lite source bundle that must build without network access.
- Very specific: line 21
Keep MODULE.bazel.lock ignored by Git when avoiding lockfile diffs in repository commits.
- Very specific: line 25
Keep dependency versions and module declarations in MODULE.bazel.
- Distinctive: line 32
Run Bazel in the managed dev container as the mapped non-root user:
- Distinctive: line 62
All delivered targets build in the intended environment without network access, using the delivered inputs rather than undeclared …
- Distinctive: line 78
Stop at the first missing module, registry, or offline build error.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bazel Vendor and Offline Delivery
When
Use this when preparing an Apollo-Lite source bundle that must build without network access.
Prerequisites
The root
.bazelrcdefines the opt-invendorconfig:common:vendor --vendor_dir=vendor- Keep
MODULE.bazel.lockignored by Git when avoiding lockfile diffs in repository commits. Bazel still needs a matching local lockfile during dependency resolution. Preserve and include that exact lockfile in the offline delivery bundle alongsidevendor/; do not omit it from the bundle. - Keep dependency versions and module declarations in
MODULE.bazel. Do not copy dependency sources there. - Resolve all delivered module versions through approved sources. Development overrides are not proof that published versions can be vendored.
Steps
Run Bazel in the managed dev container as the mapped non-root user:
bash docker/scripts/whl.sh enterFrom /apollo, vendor the complete external dependency graph:
bazel vendor --config=vendorFor a deliberately scoped offline product, pass the complete set of target patterns that the delivery must support instead. The vendored set must cover all delivered build targets and their transitive dependencies.
Deliver the source tree, vendor/, and the matching ignored
MODULE.bazel.lock together. Keep the lockfile untracked in Git; it is still
part of the delivery inputs needed to reproduce the resolved graph.
Validate the exact delivered targets in a clean environment with network access disabled, using the vendor config:
bazel build --config=vendor <delivery-target-patterns>Acceptance
- The bundle contains the source tree, matching lockfile, and vendor snapshot.
- All delivered targets build in the intended environment without network access, using the delivered inputs rather than undeclared warm-cache sources.
- Required non-Bazel dependencies are supplied for each delivery platform.
A successful build using a warm repository cache is not proof of offline completeness. The validation environment must not be able to fetch missing repositories. Re-vendor and repeat this validation when the dependency graph, delivered target set, Bazel version, or target platform changes.
Vendor mode only localizes Bazel external repositories. System packages, compilers, CUDA/cuDNN/TensorRT, drivers, model assets, maps, and other non-Bazel inputs must be supplied and validated separately for each delivery platform.
Failure handling
Stop at the first missing module, registry, or offline build error. Do not refresh the lockfile, change versions, add development overrides, or retry with different dependency flags to hide the failure without approval.
Record failures in the task report with the date, exact command, active registry/config, and first error; do not keep undated task status in this skill.
Sources
.bazelrcMODULE.bazel.gitignoredocker/scripts/whl.sh- Bazel 7.6.1 Vendor Mode
- Bazel 7.6.1 Lockfile
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.

