yoe

This skill should be used when the user asks to "diagnose a build failure", "debug a unit", "debug <unit>", "debug some unit", "fix a build", "why did the build fail", "/diagnose", or mentions a unit that failed to build. Iteratively analyzes build logs, identifies root causes, applies fixes, and rebuilds until the unit succeeds.

Use when a build needs a tool or library that Alpine Linux already packages (cross compilers, niche build tools, language runtimes without a source unit) and the instinct is to write a from-source unit. Triggers: missing-tool build errors, foreign-arch cross toolchain needs (e.g. armv7-R, riscv), questions about whether `module-alpine` already has package X, or "/pull-alpine".

This skill should be used when the user asks to "audit a unit", "review a unit", "check a unit", "/audit-unit", or wants to verify that a unit follows best practices and has no common issues. Reviews a unit for correctness, completeness, and quality.

This skill should be used when the user asks to "create a unit", "add a unit", "new unit", "package something", "/new-unit", or provides a URL or project name to be packaged for Yoe. Generates a complete Starlark .star unit file from a source URL or description.

This skill should be used when the user asks to "update a unit", "bump a unit", "upgrade a unit", "update to latest version", "/update-unit", or mentions that a unit needs a version bump. Bumps a unit to the latest upstream version with a test build.