build
Skill177 starsChanged 7 days agoApache-2.0View on GitHub
Apollo-Lite compile workflow. Use when building Apollo modules in the managed dev container or diagnosing a Bazel build failure.
169 other projects use a version of this.
Adopted by
Most recently taken up by
- IntelRealSense/librealsensetheir own version, first seen Nov 16, 2026
- realsenseai/librealsensetheir own version, first seen Nov 16, 2026
- mannobeats/hyper-tastetheir own version, first seen Nov 16, 2026
- jayden-dang/skillstheir own version, first seen Nov 16, 2026
- colinc86/glosstheir own version, first seen Nov 16, 2026
- wald21x6-ops/builder-kittheir own version, first seen Nov 16, 2026
Used with
Projects with it also use backprop, finances and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JuliusBrusseeSkillbackprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.
Also in 4 projects that use this
GerardoRdz96Skillfinances
Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".
Also in 3 projects that use this
cpiprintSkillfavicon
Generate favicons from a source image
Also in 3 projects that use this
madeehahassanSkillGo-Live
Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.
Also in 3 projects that use this
TrevokeSkilldefine
Use when a new feature request, bug report, or work request needs requirements defined before implementation
Also in 3 projects that use this
HAR5HA-7663Skillshape
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
Also in 6 projects that use this
Other versions169 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 169
- FalkorDB/FalkorDB★ 11ksame name
- realsenseai/librealsense★ 9.1ksame name
- IntelRealSense/librealsense★ 9.1ksame name
- microsoft/microsoft-ui-xaml★ 8.6ksame name
- NexaAI/nexa-sdk★ 8.5ksame name
- hathach/tinyusb★ 7.3ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- pytorch/TensorRT★ 3ksame name
159 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-evaluationSkill
- algorithm-developmentSkill
- 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
- vendorSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this only for compiling Apollo source and diagnosing compile failures.
- Distinctive: line 37
Use the wrapper for module builds:
- Very specific: line 46
Use bazel build //<target> only when a precise target is required.
- Distinctive: line 56
Verify expected artifacts and report any warnings affecting reuse or delivery.
- Distinctive: line 60
Stop and identify the first actionable error before changing commands or source.
- Distinctive: line 64
Do not compile Apollo targets outside the managed container.
- Distinctive: line 65
Do not hardcode a username or create root-owned Bazel outputs.
- Distinctive: line 66
Do not change verified build flags without a validation reason.
- Very specific: line 67
Do not refresh MODULE.bazel.lock to recover from a missing module without first inspecting the registry error and getting approval for the …
“Common” is measured: kept by at least 6 in 10 of the 155 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
Build and Compile
When
Use this only for compiling Apollo source and diagnosing compile failures. For building or publishing WheelOS container images, use the separate Container Image Build skill.
Prerequisites
From the repository root, enter the managed development container:
bash docker/scripts/whl.sh enterenterdefaults todevand starts it if needed. Run build commands in the container from/apollo, as the mapped non-root user.- Preserve the mapped user and shared cache. Never run Bazel as root or hide cache-permission problems with a temporary output root.
Steps
Build all modules with the exact wrapper command:
./apollo.sh build- Reuse the Bazel repository cache and existing build outputs. Do not use
apollo.sh cleanfor ordinary incremental builds. Use the wrapper for module builds:
./apollo.sh build <module>- The wrapper selects the configured CPU/GPU mode. Use
./apollo.sh build_gpu <module>or./apollo.sh build_opt_gpu <module>only when that build mode is specifically required. - Use
bazel build //<target>only when a precise target is required. - Module tests use
./apollo.sh test <module>. ./apollo.sh checkruns the full build, unit-test, and lint path. Use the separate commands when only one validation stage is needed.
Acceptance
- The requested targets build successfully in the intended CPU/GPU mode.
- Required tests pass when behavior changes. Build success alone does not establish runtime or release acceptance.
- Verify expected artifacts and report any warnings affecting reuse or delivery.
Failure handling
- Stop and identify the first actionable error before changing commands or source. Do not blindly retry or fix unrelated failures; request approval before expanding scope. If Bazel terminates unexpectedly, inspect its log and available memory before considering a retry.
- Do not compile Apollo targets outside the managed container.
- Do not hardcode a username or create root-owned Bazel outputs.
- Do not change verified build flags without a validation reason.
- Do not refresh
MODULE.bazel.lockto recover from a missing module without first inspecting the registry error and getting approval for the lockfile change.
Sources (SSOT)
apollo.shdocker/scripts/whl.shscripts/ci/apollo_build.sh
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.

