omnicheck-github SKILL.md skillA
omnicheck-github from nexiouscaliver/omniforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nexiouscaliver/omniforge/omnicheck-github@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nexiouscaliver/omniforge
- Path
plugins/omniforge/skills/omnicheck-github/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Jul 11, 2026
- Size
- 9,469 bytes
- Repository stars
- 4
- License
- MIT
Use when checking if PR review findings have been applied — verifies both OmniForge-generated and human reviewer comments against the current diff, posts nudge replies on unaddressed threads.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# OmniCheck
> **Verify whether requested PR changes have been applied — diff analysis + targeted nudge comments.**
Check all review comment threads on a GitHub PR against the current diff. Resolved threads are marked APPLIED. Unresolved threads are analyzed by a subagent to determine if the fix was applied silently or not at all. Unaddressed threads receive nudge replies and a summary comment.
**Core principle:** Thread status check + diff analysis + user approval gate = accurate, non-spammy follow-up.
**Announce at start:** "I'm using OmniCheck to verify findings on PR #{id}."
## Prerequisites
- `gh` CLI authenticated (`gh auth status` to verify)
- Git repository with remote pointing to GitHub
- Current working directory is in the git repo
- PR must have review comment threads
## Input Parsing
Accept any of: PR number (`136`), prefixed (`#136`), or full GitHub URL.
Extract PR ID. If URL provided, extract owner/repo and PR number.
## The Process
```
Phase 1: GATHER — fetch all threads + PR diff/data
Phase 2: ANALYZE — single subagent checks each open thread against the diff
Phase 3: REPORT — present status table, user approves nudge list
…Read the whole file at its exact version.
How to install
mdr add nexiouscaliver/omniforge/omnicheck-github@sha256:e1bb5fd6b6b6be3cThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_alzbfsjdrsn4omhf)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9469 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nexiouscaliver/omniforge · 4 stars · license MIT · pushed 2026-09-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_alzbfsjdrsn4omhf GET https://markdownregistry.com/api/v1/resolve?ref=nexiouscaliver/omniforge/omnicheck-github GET https://markdownregistry.com/api/v1/blob/e1bb5fd6b6b6be3c5ff335a7f48d818a43f40858328a1881aa13813dabd9302b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.