agentsclimarketplace

Bitbake dry run diagnostics

Skill BenGardiner/bitbake-yocto-agent-skills/bitbake-dry-run-diagnostics

Performs pre-flight validation of Yocto metadata and task graphs without executing a build. Use when checking syntax after a layer change, simulating build impact with dry-runs (-n), or verifying source availability. Do not use for troubleshooting active build failures or compiling target images.From its SKILL.md

Install
npx -y skills add BenGardiner/bitbake-yocto-agent-skills --skill bitbake-dry-run-diagnostics

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

2 things 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.
  • runs commandsInstructs the agent to run 4 commands, including `bitbake -p` and 3 more.

SKILL.md

1.6 KB, 308 tokens by cl100k_base, as published. Nobody here has run it

BitBake Diagnostic & Dry-Run Procedures

Use the following methods to validate Yocto metadata and task graphs without triggering a full build process.

1. Metadata Parsing Check

Validate syntax in .bb, .bbappend, .bbclass, and .conf files after modifying layers to ensure the environment is still sane and indexable.

  • Run command:
    bitbake -p
    

2. Execution Dry-Run

Simulate the build process for a specific target to visualize the task dependency graph and identify which tasks need to run ("dirty") versus which will be accelerated by the SState cache.

  • Run command:
    bitbake -n <target>
    

3. Dependency Expansion

Expand all variables and functions for a specific recipe to see the final parsed environment. This is critical for debugging variable overrides (e.g., _append, _remove) or determining the final value of variables like SRC_URI.

  • Run command:
    bitbake -e <target>
    

4. Source Fetch Validation

Attempt to download all remote assets required for a build without starting compilation. Use this as a pre-flight check to ensure no 404 errors or mirror issues will break a long-running build later.

  • Run command:
    bitbake -c fetchall <target>
    

What ships with it

Read from the repository

Just SKILL.md. No reference files, no 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.