ov-images/skills/debian-builder/SKILL.md
Minimal Debian 13 builder image (pixi + Node.js + build-toolchain) used as the multi-stage builder for every image based on Debian — currently debian-coder. Produces the pre-compiled pixi envs, npm globals, and cargo crates that land in the final runtime image via COPY --from. MUST be invoked before building, deploying, configuring, or troubleshooting the debian-builder image.
npx skillsauth add overthinkos/overthink-plugins debian-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.
Debian 13 counterpart of /ov-images:fedora-builder. Provides the pixi / npm / cargo build environments so downstream deb-based images (currently /ov-images:debian-coder) get pre-compiled artifacts from a dedicated builder stage without bloating the final image.
| Property | Value |
|----------|-------|
| Base | debian (which = debian:13 + our bootstrap) |
| Layers | pixi, nodejs, build-toolchain |
| Platforms | linux/amd64 |
| Registry | ghcr.io/overthinkos |
| User | user / uid 1000 (create mode — debian:13 ships no pre-existing uid-1000 account) |
/ov-images:debian — Debian 13 + our apt-get update && apt-get install -y --no-install-recommends curl ca-certificates gnupg bootstrap + go-task binary + user:user uid 1000./ov-layers:pixi — pixi package manager + env paths./ov-layers:nodejs — Node.js + npm (generic nodejs, not nodejs24 — Debian packages a current-enough version)./ov-layers:build-toolchain — gcc, g++, cmake, autoconf, ninja, pkg-config, and the full set of -dev libraries (Debian equivalents of Fedora's -devel). Used by cargo crates that link system libs (libva, x264, ffmpeg, wayland, xkbcommon, etc.).Declares builds: [pixi, npm, cargo] and is listed as debian-coder's builder for all three types via:
debian:
builder:
pixi: debian-builder
npm: debian-builder
cargo: debian-builder
During ov image build debian-coder, any layer that ships pixi.toml / package.json / Cargo.toml gets a multi-stage FROM debian-builder AS <layer>-<builder>-build section emitted by the generator, then COPY --from=<stage> --chown=${UID}:${GID} into the final image. See /ov-dev:generate for the template.
No AUR equivalent (unlike /ov-images:archlinux-builder) — AUR is an Arch-only concept.
/ov-images:fedora-builder — Fedora 43 equivalent (+ rpmfusion for x264/ffmpeg/libva headers)./ov-images:archlinux-builder — Arch Linux equivalent + yay for AUR./ov-images:ubuntu-builder — Ubuntu 24.04 equivalent; differs from this image mainly in user:ubuntu vs user:user (adopt mode — see /ov-images:ubuntu).ov image build debian-builder
ov shell debian-builder
Typically not invoked directly — it's a build-time dependency of /ov-images:debian-coder.
ov image list | grep debian-builder — image present.ov shell debian-builder -- pixi --version && node --version && gcc --version./ov-images:debian — parent base, declares the bootstrap packages in build.yml./ov-images:debian-coder — the consumer that this builder exists to serve./ov-images:fedora-builder — RPM-family sibling./ov-images:archlinux-builder — pacman + AUR sibling./ov-images:ubuntu-builder — Ubuntu 24.04 sibling./ov-layers:pixi, /ov-layers:nodejs, /ov-layers:build-toolchain/ov:build — multi-stage builders, base_user: declaration/ov:image — builds: + builder: fields/ov:generate — COPY-from stage emissionMUST be invoked when:
debian-builder itself.COPY --from errors in a debian-coder build (the source stage is this image).dotnet build type) to deb-family images.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.