Yocto dependency debugger
Skill BenGardiner/bitbake-yocto-agent-skills/yocto-dependency-debugger
Agent skills for making and fixing bitbake stuff
npx -y skills add BenGardiner/bitbake-yocto-agent-skills --skill yocto-dependency-debuggerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 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.
What its author says it does
Copied from the file, not written here
Analyzes and resolves unexpected package inclusions in Yocto images. Triggers when a specific package (e.g., graphviz, rust) is pulled into an image unnecessarily or when tracing reverse dependencies via dot files. Do not use for fixing compilation errors or debugging application-level runtime bugs.
SKILL.md
1.4 KB, as published. Nobody here has run it
Yocto Dependency Debugger
This skill provides workflows to debug and resolve unexpected package inclusions in any Yocto project.
Available Workflows
Detailed workflows are available in the references/ directory. Read the appropriate reference file based on your debugging step:
-
You need to trace why a package was included: Read
references/dependency-graphing.md(Explains usingbitbake -gand.dotfiles). -
You need to check how a recipe pulls in dependencies: Read
references/recipe-inspection.md(Explains checkingPACKAGECONFIGand defaults). -
You need to drop an unwanted dependency: Read
references/configuration-modification.md(Explains using overrides to remove features). -
You need to verify your configuration changes: Read
references/environment-verification.md(Explains usingbitbake-getvarandbitbake -e).
Out of Scope
- To fix build errors or cache issues, use the
bitbake-debuggerskill. - To locate where a recipe comes from, use the
yocto-recipe-locatorskill.