ov-foundation/skills/fedora-builder/SKILL.md
Builder image with pixi, Node.js, and C/C++ build toolchain. Used as the default builder for multi-stage image builds. MUST be invoked before building, deploying, configuring, or troubleshooting the fedora-builder image.
npx skillsauth add overthinkos/overthink-plugins fedora-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Builder image with package managers and compilation tools. Default builder for pixi, npm, and cargo multi-stage builds (declared via builds: [pixi, npm, cargo]).
| Property | Value | |----------|-------| | Base | fedora | | Layers | rpmfusion, pixi, nodejs, build-toolchain | | Platforms | linux/amd64 | | Registry | ghcr.io/overthinkos |
fedora (quay.io/fedora/fedora:43)rpmfusion — RPM Fusion free + nonfree repo configuration. Applied first so subsequent layers can dnf install packages from RPM Fusion (e.g. x264-devel, ffmpeg-devel, libva-devel)pixi — pixi package manager + env pathsnodejs — Node.js + npmbuild-toolchain — gcc, cmake, autoconf, ninja, git, pkg-config, plus the smithay/cargo build deps (rust, cargo, clang-devel, nasm, wayland-devel, libva-devel, x264-devel, ffmpeg-devel, pixman-devel, …) needed for builder-stage compilation of Wayland compositors like pixelflux. See /ov-coder:build-toolchain for the full grouped list.The build-toolchain layer's dnf install references packages that live in RPM Fusion free
(libva-devel, x264-devel, ffmpeg-devel). These are required to build pixelflux from
source (its libva-sys, x264-sys, and ffmpeg-sys-next cargo crates link against the
system libs). Without rpmfusion applied first, those dnf install calls would fail.
See /ov-selkies:selkies (Patched pixelflux build pipeline) for the consumer story.
This image is referenced in defaults.builders as the builder for pixi, npm, and cargo multi-stage builds. It declares builds: [pixi, npm, cargo] to advertise its capabilities. The generator uses it as the FROM stage in multi-stage builds, providing build tools without bloating final images.
ov image build fedora-builder
ov shell fedora-builder
/ov-foundation:pixi — Python package management foundation/ov-coder:nodejs — Node.js runtime and npm/ov-coder:build-toolchain — C/C++ compilation tools/ov-foundation:fedora — parent baseAfter ov image build:
ov image list — image appears in listov shell fedora-builder — interactive shell worksMUST be invoked when the task involves the fedora-builder image, multi-stage builds, or build cache configuration. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov-build:build — build.yml vocabulary (distros, builders, init-systems)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.