yocto-recipe-maintenance

Yocto recipe maintenance skill for AI coding agents. Use for creating, updating, auditing, or reviewing .bb and .bbappend files; package version bumps; dependency, license, PACKAGECONFIG, configure flag, patch, CVE, runtime dependency, package split, and cross-distro packaging comparisons against OpenEmbedded, Alpine, Buildroot, Debian, or upstream sources.

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-recipe-maintenance

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

3 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Yocto Recipe Maintenance

Workflow

Identify the target Yocto release, layer, recipe name, version, provider, and image impact.

Search local layers and the OpenEmbedded Layer Index before creating new metadata.

Compare how OE-Core/meta-openembedded, Alpine, Buildroot, Debian, and upstream package the same software when useful.

Inspect upstream source for build system, license files, tags/releases, dependencies, optional features, and patches.

Make the smallest metadata change: new recipe, .bbappend, version bump, dependency fix, PACKAGECONFIG, patch refresh, or package split.

Validate with BitBake introspection and a targeted build.

Maintenance Modes

Create recipe: choose build class, source, SRCREV/checksums, license, dependencies, package config, and install behavior.

Update recipe: bump version/source revision, refresh checksums, inspect release notes, review patches, and test reverse dependencies.

Audit recipe: review missing deps, runtime deps, license, QA risks, package splits, bundled libraries, patch freshness, and security issues.

Review append: ensure the append applies only where intended and does not mask upstream behavior broadly.

References

recipe-maintenance-playbook.md: create/update/audit workflow and cross-distro checks.

Guardrails

Do not create a new recipe if a maintained layer already provides the package and a .bbappend is enough.

Do not guess license metadata; inspect upstream files and use exact LIC_FILES_CHKSUM.

Do not disable features just to make a build pass without explaining product impact.

Do not install missing host tools globally; model them as native dependencies or disable nonessential generated docs/tests.