Yocto ci release
Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-release
Claude Agent Skills for Yocto Project, OpenEmbedded, and BitBake workflows - AI coding assistant skills for recipes, layers, images, BSPs, SDKs, metadata, QA, sstate, and build troubleshooting.
npx -y skills add prashantdivate/awesome-yocto-ai-agent-skills --skill yocto-ci-releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
Yocto CI, reproducible build, and release engineering skill for AI coding agents. Use for kas, repo manifests, Git submodules, containerized builds, CI runners, downloads and sstate caches, hash equivalence, PR build gates, QEMU tests, hardware smoke tests, artifact publishing, SDK releases, SBOM/license manifests, release notes, and version pinning.
SKILL.md
1.4 KB, as published. Nobody here has run it
Yocto CI Release
Workflow
- Identify source orchestration:
kas,repo, submodules, manifest repo, or monorepo. - Pin every layer and external source needed for reproducibility.
- Separate caches from build output:
DL_DIR,SSTATE_DIR, hash equivalence, container caches, and artifacts. - Build the smallest useful CI matrix: parse, recipe smoke, image, SDK, QEMU/testimage, hardware smoke where available.
- Publish signed and checksummed artifacts with machine, distro, image, git refs, build config, license data, and SBOM if enabled.
- Keep secrets out of
local.conf, logs, and artifacts.
References
- ci-release-playbook.md: CI pipeline patterns, cache strategy, release artifact checklist.
Guardrails
- Do not use floating branch refs for release builds.
- Do not persist
tmp/as a cache unless the project explicitly accepts the fragility. - Do not publish images without checksums and provenance.
- Do not run hardware flashing in CI without explicit device targeting and recovery controls.