Yocto ci kas build
Skill prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-kas-build
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-kas-buildAssembled 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
Official-doc-first Yocto CI, kas, and reproducible build workflow support for AI coding agents. Use when creating or modifying kas YAML files, CI pipelines, containerized Yocto builds, shared DL_DIR or SSTATE_DIR caching, build matrix jobs, smoke builds, artifact publishing, reproducibility checks, or repository onboarding workflows for Yocto/OpenEmbedded projects.
SKILL.md
2.0 KB, as published. Nobody here has run it
Yocto CI Kas Build
Core Workflow
- Inspect existing build entrypoints first:
kas*.yml, wrapper scripts, Dockerfiles, CI YAML, README build instructions, and release scripts. - Identify release, layer refs,
MACHINE,DISTRO, image targets, SDK targets, and artifact expectations. - Keep repository source orchestration explicit: kas repos, branch pins, commit pins, lockfiles, submodules, or repo manifests.
- Keep
DL_DIRandSSTATE_DIRcache policy explicit and separate from generated build output. - Use CI jobs to validate representative machines/images, not every possible target unless requested.
- Publish artifacts with checksums, provenance, manifests, and release metadata.
Use yocto_ci_doc_router.py with a topic name for official documentation links.
References
- kas-patterns.md: kas file structure, repos, layers, local config, and lock/pin patterns.
- ci-cache-patterns.md: downloads, sstate, hash equivalence, runner storage, and cache keys.
- build-reproducibility.md: source pinning, host/container policy, artifacts, and release metadata.
Guardrails
- Do not hardcode host-specific absolute paths.
- Do not commit generated build output,
tmp,sstate-cache,downloads, or deploy artifacts unless the repo intentionally tracks fixtures. - Do not use floating refs for release builds unless the workflow is explicitly non-release.
- Do not leak mirror credentials, signing keys, or private registry tokens into CI logs.