omarchy-development

Develop and test Omarchy source changes in disposable KVM/QEMU virtual machines.

2|Updated May 14, 2026
One-click install
npx skills add https://github.com/AnthonyPoschen/agent-skills --skill omarchy-development-anthonyposchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omarchy-development
Source: https://github.com/AnthonyPoschen/agent-skills/tree/main/skills/omarchy-development
Command: npx skills add https://github.com/AnthonyPoschen/agent-skills --skill omarchy-development-anthonyposchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing Omarchy source changes directly on your host machine risks breaking your daily-driver installation. This Skill provides a safe, isolated workflow for developing, testing, and debugging Omarchy code in disposable virtual machines while keeping the host system untouched. ## Core Features & Use Cases - Isolated VM Testing: Create disposable KVM/QEMU overlay VMs registered in Virtual Machine Manager via libvirt, built from a reusable base image. - Guest-Side Source Linking: Clone feature branches inside the guest and use omarchy dev link there, never on the host. - Safe Lifecycle Management: Define, start, shut down, undefine, and delete overlay VMs through libvirt with strict safety checks. - Use Case: You are fixing a bug in Omarchy's QML shell. Run qmllint and shell tests locally, then spin up an overlay VM, link your branch inside the guest, and visually verify the fix without touching your host installation. ## Quick Start Ask the agent to set up a disposable Omarchy test VM for your feature branch and verify your shell changes inside it.

Frequently Asked Questions about omarchy-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Omarchy source changes without breaking my host system?▼

Create a disposable qcow2 overlay VM from a reusable base image and register it with libvirt. Clone your feature branch inside the guest and run omarchy dev link there, leaving the host installation completely untouched.

How do I create a QEMU overlay VM for Omarchy development?▼

Use qemu-img create with the -b flag to build a qcow2 overlay backed by your base.qcow2, copy the OVMF vars file, then define a libvirt domain XML with KVM, UEFI, SPICE graphics, and user-mode networking.

Why does my Omarchy VM guest have no network with libvirt NAT?▼

The libvirt default NAT network causes a guest DHCP failure in this setup. Use QEMU user-mode networking with a virtio interface instead, which gives the guest outbound Internet for cloning and package operations.

Can I use omarchy dev link on my host machine?▼

No, this workflow forbids running omarchy dev link, restarting the shell, or rebooting the host to test source changes. Development linking happens only inside the disposable guest VM so the host stays on its packaged version.

How do I safely delete an Omarchy test VM?▼

Confirm the VM is shut off via virsh domstate, undefine the libvirt domain, verify it no longer appears in virsh list --all, then delete only that specific overlay directory. Never delete the reusable base disk.