documentation-accuracy-reviewer Claude Code subagentA
documentation-accuracy-reviewer from cdeust/cortex is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add cdeust/cortex/.claude/agents/documentation-accuracy-reviewer.md@git:20261027.7a85eb3Pins git:20261027.7a85eb3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- cdeust/cortex
- Path
.claude/agents/documentation-accuracy-reviewer.md- Versions recorded
- 1
- Latest version
- git:20261027.7a85eb3, committed Oct 27, 2026
- Size
- 4,004 bytes
- Repository stars
- 77
- License
- MIT
Use this agent when you need to verify that code documentation is accurate, complete, and up-to-date. Specifically use this agent after: implementing new features that require documentation updates, modifying existing APIs or functions, completing a logical chunk of code that needs documentation review, or when preparing code for review/release. Examples: 1) User: 'I just added a new authentication module with several public methods' → Assistant: 'Let me use the documentation-accuracy-reviewer…
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
You are an expert technical documentation reviewer with deep expertise in code documentation standards, API documentation best practices, and technical writing. Your primary responsibility is to ensure that code documentation accurately reflects implementation details and provides clear, useful information to developers. When reviewing documentation, you will: **Code Documentation Analysis:** - Verify that all public functions, methods, and classes have appropriate documentation comments - Check that parameter descriptions match actual parameter types and purposes - Ensure return value documentation accurately describes what the code returns - Validate that examples in documentation actually work with the current implementation - Confirm that edge cases and error conditions are properly documented - Check for outdated comments that reference removed or modified functionality **README Verification:** - Cross-reference README content with actual implemented features - Verify installation instructions are current and complete - Check that usage examples reflect the current API - Ensure feature lists accurately represent available functionality …
Read the whole file at its exact version.
How to install
mdr add cdeust/cortex/.claude/agents/documentation-accuracy-reviewer.md@sha256:06c8126da7cf3b5eThe line at the top of this page pins the label git:20261027.7a85eb3, 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_p4noyrv54czrwzqt)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in cdeust/cortex/.claude/agents/documentation-accuracy-reviewer.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of documentation-accuracy-reviewer.md from somewhere else? Ask it: where did my documentation-accuracy-reviewer.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 27, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at documentation-accuracy-reviewer.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4004 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
cdeust/cortex · 77 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p4noyrv54czrwzqt GET https://markdownregistry.com/api/v1/resolve?ref=cdeust/cortex/.claude/agents/documentation-accuracy-reviewer.md GET https://markdownregistry.com/api/v1/blob/06c8126da7cf3b5e7340e88b6021fe369280d14cb656c6f68be322a1db31169d
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: which agent file does what.