omnicheck-gitlab SKILL.md skillA
omnicheck-gitlab 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-gitlab@git:20260910.4f70609Pins git:20260910.4f70609 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-gitlab/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260910.4f70609, committed Sep 10, 2026
- First version recorded
- Apr 16, 2026
- Size
- 15,658 bytes
- Repository stars
- 4
- License
- MIT
Use when checking if MR 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 MR changes have been applied — diff analysis + targeted nudge comments.**
Check all discussion threads on a GitLab MR 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. When every finding is verified applied, offer to approve the MR (as the OmniCheck bot when `OMNICHECK_BOT_TOKEN` is set).
**Core principle:** Thread status check + diff analysis + user approval gate = accurate, non-spammy follow-up — and, when clean, a one-keystroke approval.
**Announce at start:** "I'm using OmniCheck to verify findings on MR !{id}."
## Prerequisites
- `glab` CLI authenticated (`glab auth status` to verify)
- Git repository with remote pointing to GitLab
- Current working directory is in the git repo
- MR must have discussion threads
## Input Parsing
Accept any of: MR number (`136`), prefixed (`!136`), or full GitLab URL.
Extract MR ID. If URL provided, extract project path and MR IID.
## The Process
```
Phase 1: GATHER — fetch all threads + MR diff/data
…Read the whole file at its exact version.
How to install
mdr add nexiouscaliver/omniforge/omnicheck-gitlab@sha256:a13a073c948da1f0The line at the top of this page pins the label git:20260910.4f70609, 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_65dgnqosqeaxwvqw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 16, 2026 and Sep 10, 2026, about one every 49 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.4f70609 latest | 2026-09-10 | 4f70609 | 15,658 B | A | view · diff |
| git:20260805.fb5425c | 2026-08-05 | fb5425c | 12,154 B | A | view · diff |
| git:20260416.eeb64b0 | 2026-04-16 | eeb64b0 | 8,692 B | A | view · diff |
| git:20260416.e1a685c | 2026-04-16 | e1a685c | 8,284 B | A | view |
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 (15658 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_65dgnqosqeaxwvqw GET https://markdownregistry.com/api/v1/resolve?ref=nexiouscaliver/omniforge/omnicheck-gitlab GET https://markdownregistry.com/api/v1/blob/a13a073c948da1f01f4bf74c0df09748cedb362a16a5bc99dc15746ff409258c
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.