agentsclimarketplace
Sign in

Yocto build debug

Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-build-debug

Advanced Yocto Project build and debug skill for AI coding agents. Use for BitBake parse failures, fetch failures, patch/configure/compile/install/package failures, QA errors, missing providers, layer dependency errors, sstate/hash/signature problems, long build times, disk pressure, host dependency issues, TMPDIR confusion, and commands such as bitbake, bitbake-layers, bitbake -e, bitbake -g, bitbake-diffsigs, devtool, oe-pkgdata-util, runqemu, and testimage.From its SKILL.md

Install
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-build-debug

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 459 tokens by cl100k_base, as published. Nobody here has run it

Yocto Build Debug

Workflow

  1. Identify the build entrypoint: Makefile, kas, repo, oe-init-build-env, container script, CI job, or vendor wrapper.
  2. Confirm MACHINE, DISTRO, BBLAYERS, TMPDIR, DL_DIR, SSTATE_DIR, and target image/recipe.
  3. Reproduce the smallest failing command. Prefer parse, fetch, or one task over a full image rebuild.
  4. Inspect logs before editing metadata. Use yocto_log_triage.py with the build directory for a quick scan.
  5. Classify the failure: parse, layer, provider, fetch, patch, configure, compile, install, package, QA, image, test, or signature.
  6. Route metadata questions to $bitbake-metadata; route board boot/deploy issues to $yocto-deploy-flash or $yocto-bsp-bringup.

Commands

bitbake-layers show-layers
bitbake-layers show-recipes RECIPE
bitbake-layers show-appends
bitbake -e RECIPE
bitbake -c listtasks RECIPE
bitbake -c TASK -f RECIPE
bitbake -g RECIPE
bitbake-diffsigs SIGDATA_A SIGDATA_B
oe-pkgdata-util list-pkgs

References

Guardrails

  • Do not recommend deleting tmp/ or sstate-cache/ until narrower evidence has been checked.
  • Do not silence QA with INSANE_SKIP until the package/file/license root cause is known.
  • Do not assume deploy output is under tmp/; many builds use tmp-glibc, multiconfig paths, or custom TMPDIR.
  • Do not change provider/version policy globally without checking affected recipes and images.

What ships with it: 4 files

5.8 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.