omarchy-plugin-test
Test an Omarchy plugin
Inspect the actual changed checkout, including relevant untracked files. Select checks for the changed behavior and complete required repository checks; a tooltip edit does not need a new state-machine suite.
Resolve <skill-dir> to this skill's directory:
python3 "<skill-dir>/scripts/validate_plugin.py" /absolute/path/to/plugin
python3 "<skill-dir>/scripts/validate_plugin.py" --json --security /absolute/path/to/plugin
The portable checker does not execute plugin code. Schema checks and advisory security diagnostics do not establish runtime correctness or certify safety. Reconcile differences with the installed omarchy plugin validate <path> and current marketplace contract.
Verify relevant layers: manifest/path; exact Qt/Quickshell imports; fixture/unit behavior; live discovery, enablement, visible interaction, IPC, reload and disablement; installation/update/removal for lifecycle changes. Include tray popout placement, language switching/RTL and Qt 6.12 palette lookup when affected.
For persistent-state fixes, use the upgrade fixtures against the production migration. For external text, use the optional plain-text check.
Load test matrix or QML testing as needed. For optional capability policies, baseline tools and disposable desktops, read validation options. For marketplace findings, read review response. Companion tools are optional; do not install them just to satisfy a workflow.