{"slug": "ai-in-the-build-loop-yoe", "title": "AI in the Build Loop [yoe]", "summary": "Yoe build system integrates Claude Code AI skills into the build loop, allowing developers to diagnose and fix build errors via a terminal UI or Claude session. The 'diagnose' skill reads build logs and automatically corrects issues, demonstrating how AI agents can handle complex build-system reasoning that humans find difficult.", "body_md": "A build system is a lot of small pieces — feeds, units, dependencies, task\nsteps, sandboxes. None of it is hard on its own. The hard part is holding all of\nit in your head at once, which is exactly what humans are bad at and agents are\ngood at. The [latest video](https://youtu.be/nfG_UTerYeo) shows how `[yoe]`\n\nuses\nthat: it ships Claude Code skills you install into your project, and wires a\ndiagnose step into the build loop.\n\nThe [AI skills page](https://docs.yoebuild.org/ai-skills.html) covers both\npaths.\n\nRun `yoe skills install`\n\ninside your project and it drops the skills into your\n`.claude/`\n\nfolder. `yoe init`\n\nnow does this by default. Keeping them local lets\nyou list, update, and diff them against your own edits. Note that `update`\n\noverwrites, so rename a skill first if you’ve customized it.\n\nThe other path is the Claude Code plugin marketplace: add the `[yoe]`\n\nmarketplace, reload, and skills like `diagnose`\n\nand `new-unit`\n\nshow up as\nplugins.\n\nSeveral skills ship in the set. Many are still ideas, but `diagnose`\n\nand\n`new-unit`\n\nare in daily use, and the rest will fill in over time.\n\n`d`\n\nto diagnoseThe demo: add a bad `echo make error`\n\ntask step to the `ca-certificates`\n\nunit.\n`[yoe]`\n\nsees the unit is no longer cached, rebuilds it, and the build fails on\nthe first step. You could shell out and hunt for the problem yourself. Instead,\npress ** d**.\n\nThat runs the `diagnose`\n\nskill and hands it the build log, so the agent starts\nfrom the evidence instead of searching for it. It reads the log, finds the bad\nline, removes it from the unit, and the rebuild succeeds — all without leaving\nthe `[yoe]`\n\nterminal UI.\n\nYou can also run it from a Claude session: say “diagnose the unit that fails to build” and get the same result. The TUI path keeps you in the build loop; the Claude path keeps your agent and build side by side. Either way, the agent gets the log instead of guessing.\n\nThis is a trivial example on purpose — a one-line error, a one-line fix. The\npoint is the wiring, not the bug. The same pattern reaches harder problems as\nthe skills mature: porting BSPs from Yocto, expanding `new-unit`\n\n, and pulling\nunits across from Alpine, Debian, and other systems.\n\nThe full set of walkthroughs is on the\n[Videos page](https://yoebuild.org/videos/). A few ways to go further:\n\n`/new-machine`\n\nand `/new-module`\n\nAI skills", "url": "https://wpnews.pro/news/ai-in-the-build-loop-yoe", "canonical_source": "https://yoebuild.org/blog/ai-integration/", "published_at": "2026-06-11 00:00:00+00:00", "updated_at": "2026-06-18 17:40:31.041035+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents", "large-language-models"], "entities": ["Yoe", "Claude Code", "Anthropic"], "alternates": {"html": "https://wpnews.pro/news/ai-in-the-build-loop-yoe", "markdown": "https://wpnews.pro/news/ai-in-the-build-loop-yoe.md", "text": "https://wpnews.pro/news/ai-in-the-build-loop-yoe.txt", "jsonld": "https://wpnews.pro/news/ai-in-the-build-loop-yoe.jsonld"}}