g-doc-review SKILL.md skillB
g-doc-review from onlygian/g-forge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add onlygian/g-forge/g-doc-review@git:20260902.43671e4Pins git:20260902.43671e4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- onlygian/g-forge
- Path
skills/g-doc-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260902.43671e4, committed Sep 2, 2026
- First version recorded
- Jul 15, 2026
- Size
- 11,241 bytes
- Repository stars
- 4
- License
- GPL-3.0
Documentation review gate. Dispatches the doc-reviewer agent on the changed file set to check documentation currency against the code it describes, then issues a standalone DOCS READY or DOCS HOLD verdict. On DOCS READY it writes the doc-approval sentinel that the commit gate checks for doc/mixed commits. Read-only on project content — it judges and gates, never writes docs. Distinct from /g-review (code review) and /g-docs (audits and generates docs).
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
**Announce:** "Using g-doc-review to run the documentation review gate." You are running the documentation merge gate. It has its own verdict — **DOCS READY** or **DOCS HOLD** — separate from /g-review's code verdict. This skill judges documentation currency only; it never writes or fixes docs. Execute these steps in order. ## Step 1 — Build the review pack Locate the shared pack builder: Glob for `skills/g-review/scripts/build-review-pack.sh` under `~/.claude/plugins/cache/g-forge/g-forge/` (in a plugin-source checkout, use the repo's own copy). Run it from the project root: `bash <script> --gate doc --slug <slug>` — with `--path <path>` when a path argument was provided (e.g. `/g-doc-review src/services`; the slug is then the slugified path), `--closes <file>` when this run claims to close prior findings, and `--reuse <code pack dir>` when /g-review built a pack for the same tree this session (adopted only when `PACK_TREE` still matches and no `--path` is set). Interpret its `KEY: value` output — the changed set, diff, full-file `slices/`, and MANIFEST are on disk; the union/fallback/mainline mechanics and ADR-004 rationale live in the script and… …
Read the whole file at its exact version.
How to install
mdr add onlygian/g-forge/g-doc-review@sha256:90455f41b755fac8The line at the top of this page pins the label git:20260902.43671e4, 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_r3svfmmmhwfllryw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 15, 2026 and Sep 2, 2026, about one every 12 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260902.43671e4 latest | 2026-09-02 | 43671e4 | 11,241 B | B | view · diff |
| git:20260830.45641b7 | 2026-08-30 | 45641b7 | 16,408 B | A | view · diff |
| git:20260828.2714603 | 2026-08-28 | 2714603 | 15,693 B | A | view · diff |
| git:20260820.df2ca1b | 2026-08-20 | df2ca1b | 15,395 B | A | view · diff |
| git:20260715.c94e29b | 2026-07-15 | c94e29b | 7,416 B | A | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11241 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
onlygian/g-forge · 4 stars · license GPL-3.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r3svfmmmhwfllryw GET https://markdownregistry.com/api/v1/resolve?ref=onlygian/g-forge/g-doc-review GET https://markdownregistry.com/api/v1/blob/90455f41b755fac8e5d2d4976a2ac3ab4e11358814f76795dd9a929f44440420
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.