القائمة
Use as a QEMU flow primitive to prove QEMU device, board, TCG, or runtime behavior with qtest, traces, logs, replay, and boot/workload evidence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | qemu-model-verification |
| description | Use as a QEMU flow primitive to prove QEMU device, board, TCG, or runtime behavior with qtest, traces, logs, replay, and boot/workload evidence. |
Use this skill when a QEMU model, board, TCG change, or debug hypothesis must be proven rather than merely built.
As a flow primitive, use this skill to turn the result of a build, image package, boot run, trace, or debugger session into a clear PASS, FAIL, or INCONCLUSIVE claim.
This primitive owns only evidence interpretation and reporting. It consumes a
behavior claim, evidence paths, commands, hashes, traces, and logs supplied by
the caller, then reports PASS, FAIL, or INCONCLUSIVE. It does not choose
build, qtest, debug, boot, or iterative-fix workflow steps.
Do not produce source code intended for QEMU upstream submission. Do not add DCO or review trailers.
Use the lowest rung that proves the claim:
Do not claim device correctness from a boot banner alone.
Record in .oh-my-qemu/<task-slug>/evidence.md:
Classify before changing model code:
Only topology, model-semantics, and TCG categories usually justify source changes.
For accelerators or reverse-engineered paths:
Use:
PASS|FAIL|INCONCLUSIVE: <gate>
Command: <exact command>
Artifacts: <paths under .oh-my-qemu/<task-slug>/>
Evidence: <decisive lines or summary>
Proves: <specific claim>
Does not prove: <remaining gap>
docs/devel/code-provenance.rst.docs/devel/testing/main.rst.docs/devel/testing/qtest.rst.docs/devel/tracing.rst.docs/system/replay.rst.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.