What problem does it solve? Omarchy plugin verification layers have repeatedly reported success without checking anything: gates counted SKIP as PASS, static linters passed broken QML contracts, and renders used seeded fixtures that hid dead endpoints. This Skill runs a pre-submission lane that refuses to report green for anything it did not actually check, distinguishing NOT APPLICABLE from UNPROVEN and refusing to emit a submission when any applicable check could not run. ## Core Features & Use Cases - Five-layer verification: runs the vendored gate lane (checked against canonical first), the repo's offline test suite, rig validation with omarchy-plugin-validate and qmllint, a real headless shell render treating any QML warning as a finding, and a live first-run test with empty cache and real network for plugins that fetch data. - Delegated judgment: spawns a read-only coverage-reporter agent for accounting and a separate submission-auditor agent for qualitative review, then combines results into exactly one verdict: CLEAN, FINDINGS, or INCONCLUSIVE. - Submission emission with refusal: only on CLEAN does it print the marketplace issue body per the submission format, including the coverage fraction as evidence; it never files the issue itself. - Use Case: Before pushing a plugin change or filing a marketplace verify request, run the lane to learn what your green CI actually covers, and get a defensible submission body or a named list of unproven checks with the commands that resolve them. ## Quick Start Ask the assistant to run /omarchy-ship with your plugin directory or name, for example "/omarchy-ship bazaar", to run the full lane and get a verdict.
