skills.rest
mtolhuys
mtolhuysCOMMUNITY
Explore all skills by this author →
Website𝕏@m_tolhuijsGitHub

omarchy-plugin-validation-watch

Diagnose stalled Omarchy marketplace plugin submissions by comparing validated commits against repository HEAD.

3|Updated Sep 12, 2026
Search Tags:#cli#github issues#commit validation#omarchy#plugin marketplace#submission tracking#omakit
One-click install
npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-validation-watch-mtolhuys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omarchy-plugin-validation-watch
Source: https://github.com/mtolhuys/omakit/tree/main/skills/omarchy-plugin-validation-watch
Command: npx skills add https://github.com/mtolhuys/omakit --skill omarchy-plugin-validation-watch-mtolhuys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires omakit.

What problem does it solve? Omarchy marketplace plugin submissions often go quiet after fixes are pushed, because pushing code or commenting on the issue never re-triggers validation. This Skill checks whether the commit the marketplace validated has fallen behind the repository and names the single action that re-runs validation. ## Core Features & Use Cases - Staleness Diagnosis: Runs omakit watch to compare the marketplace-validated commit with the plugin repository's current HEAD and returns a verdict such as stale, current, wrong-repository, refused, or unknown. - Batch Discovery: Uses --all --json or --list --json to check every open marketplace issue authored by the signed-in GitHub account without waiting on keyboard input. - Retry Edit Protocol: Guides a safe issue-body edit using the body rendered by omakit submit --body-out, with a diff check so only Maintainer notes may change, preventing typos in the Repository URL. - Use Case: A plugin author pushed fixes five days ago but the submission issue shows no progress; the Skill reveals the validated commit is stale and walks through editing the issue body to re-trigger validation. ## Quick Start Ask the AI to check why your Omarchy marketplace submission issue has gone quiet by running omakit watch against the issue URL and your plugin repository.

Frequently Asked Questions about omarchy-plugin-validation-watch

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

FAQPage Schema
How do I check why my Omarchy plugin submission is stuck?▼

Run omakit watch with the marketplace issue URL and your plugin repository path. It compares the commit the marketplace validated against your repository's current HEAD and returns a verdict naming the one action that re-runs validation.

Why doesn't pushing a fix re-trigger marketplace validation?▼

The marketplace validates one exact commit, and the only workflow trigger is editing the issue body. There is no issue_comment trigger, so pushing commits or commenting on the issue does nothing to start a new validation.

How do I re-run validation on a stale Omarchy submission?▼

Edit the issue body using the retry edit protocol: re-run omakit submit with --body-out, diff the new body against the current issue body so only Maintainer notes differ, then apply it with gh issue edit. Never retype the Repository URL by hand.

Does omakit watch modify my GitHub issue or repository?▼

No, omakit watch is read-only and cannot comment, label, or edit anything. It reads the default branch through the GitHub REST API using your gh login credential, falling back to the public commit feed without one.

What does the wrong-repository verdict mean in omakit watch?▼

It means the issue's Repository URL does not match the plugin's origin, so the marketplace is validating a different repository or none. Fix it with the retry edit protocol, since the body omakit submit renders carries the correct origin.

Can I use omakit watch without a GitHub token?▼

Yes, without a credential it falls back to the public commit feed. When a credential exists it is taken from the gh login, which honours GH_TOKEN and GITHUB_TOKEN; run omakit doctor and read the github.auth line to see the source.

Related Skills

Explore More Software Engineering Skills→
WordPressBugBountyWordPressBugBounty

woo-marketplace-submission

Generate WooCommerce.com Marketplace submission content and packaging guidance for plugin vendors.

Official
Advanced
mattbobambrosemattbobambrose
1

rename-plugin

Rename plugins across marketplace files and update catalog entries.

Community
Intermediate
kitaekattkitaekatt
3

plugin-ecosystem

Generate an HTML visualization of installed Claude Code plugin marketplaces and metadata.

Community
Intermediate
Clawdi-AIClawdi-AI
4

github

Manage GitHub issues, pull requests, and CI/CD via the gh CLI.

Official
Intermediate