メニュー
Use for building Linux kernels for QEMU boot testing, including defconfig selection, cross compile variables, Docker or host toolchains, Image, DTB, modules, initramfs inputs, output hashes, and provenance records.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use as the first step for any non-trivial QEMU task. Produces a small implementation or debugging plan under a .oh-my-qemu task workspace with acceptance criteria, scope boundaries, artifact policy, and verification gates.
Use for QEMU board, SoC, machine, memory map, boot path, FDT/ACPI, and IRQ topology modeling. Extends qemu-plan and qemu-rlcr-loop; board work must add or extend qemu-qtest coverage for verification.
Use for booting Linux in QEMU through either direct kernel loading or firmware and bootloader stages, selecting the path from task inputs while preserving provenance, boot logs, debug handoff, and verification evidence.
Use for QEMU peripheral, accelerator, MMIO, qdev, or SysBusDevice modeling. Extends qemu-plan and qemu-rlcr-loop; register-bank modeling must use QEMU's registerinfo framework and qtest verification.
Use for adapting a QEMU TCG host backend, including optional op support, constraints, register allocation, host code emission, qemu_ld/st, atomics, and vector ops. Extends qemu-plan and qemu-rlcr-loop.
Use for adding, reviewing, or debugging a guest ISA instruction in a QEMU TCG frontend. Extends qemu-plan and qemu-rlcr-loop; this skill only defines frontend decode/translation decisions.
SOC 職業分類に基づく
| name | qemu-kernel-build |
| description | Use for building Linux kernels for QEMU boot testing, including defconfig selection, cross compile variables, Docker or host toolchains, Image, DTB, modules, initramfs inputs, output hashes, and provenance records. |
Use this primitive when a QEMU task needs a Linux kernel artifact to boot or debug a modeled board.
This primitive owns only Linux kernel build actions and output evidence: configuration, toolchain, build command, logs, produced kernel artifacts, modules, DTBs, and hashes. It consumes a kernel source tree and build goal supplied by the caller and does not choose provenance, packaging, or boot workflow steps.
Record and verify:
.config change;Use the kernel tree's preferred commands. Typical Linux patterns are:
make ARCH=<arch> O=<out> <defconfig>
make ARCH=<arch> O=<out> CROSS_COMPILE=<prefix> -j$(nproc) Image modules dtbs
If Docker is used, record image, mounts, user, working directory, and the command run inside the container.
.oh-my-qemu/<task-slug>/logs/.