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.

Jump to install

Repository: prashantdivate/awesome-yocto-ai-agent-skills
Last source activity: July 7, 2026 at 12:50
Detected SKILL.md language: English
Stars: 4
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-build-debug

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

5 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Yocto Build Debug

Workflow

Identify the build entrypoint: Makefile, kas, repo, oe-init-build-env, container script, CI job, or vendor wrapper.

Confirm MACHINE, DISTRO, BBLAYERS, TMPDIR, DL_DIR, SSTATE_DIR, and target image/recipe.

Reproduce the smallest failing command. Prefer parse, fetch, or one task over a full image rebuild.

Inspect logs before editing metadata. Use yocto_log_triage.py with the build directory for a quick scan.

Classify the failure: parse, layer, provider, fetch, patch, configure, compile, install, package, QA, image, test, or signature.

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

failure-playbook.md: failure categories and fixes.

performance-cache.md: sstate, downloads, disk, parallelism, and reproducibility debugging.

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.

name

yocto-build-debug

description