One-click install
npx skills add https://github.com/zeikar/hyperclaude --skill hyper-docs-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hyper-docs-review
Source: https://github.com/zeikar/hyperclaude/tree/main/skills/hyper-docs-review
Command: npx skills add https://github.com/zeikar/hyperclaude --skill hyper-docs-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents documentation drift by running an accuracy-focused Codex review after docs are changed, catching stale claims, missing coverage, and broken or inconsistent links before they ship.

Core Features & Use Cases

  • Documentation accuracy gate: Checks drift between docs and code, documentation completeness, and contradictions across documents.
  • Broken/suspect link detection: Flags broken or suspect links as part of the accuracy review.
  • Accuracy-only scope: Excludes prose/style feedback and focuses specifically on correctness, coverage, and consistency.

Quick Start

Run the skill on the docs you updated by invoking /hyperclaude:hyper-docs-review docs/api.md.

Frequently Asked Questions about hyper-docs-review

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

FAQPage Schema
How do I check documentation accuracy after editing code?▼

Run a post-sync verification review that catches documentation drift from code, identifies completeness gaps, and surfaces broken or suspect links to ensure cross-document consistency.

What is documentation drift detection?▼

Documentation drift detection is the process of identifying inaccuracies in documentation caused by recent code edits, flagging stale claims, missing coverage, and contradictions across documents to maintain accuracy.

How do I review a documentation directory for cross-doc consistency?▼

Review a documentation directory for cross-doc consistency by running an accuracy-focused gate that checks for contradictions across documents, verifies completeness, and flags broken links without evaluating prose style.

Can I check for broken links without getting prose style feedback?▼

Yes, you can check for broken links using an accuracy-only review scope that explicitly excludes prose and style feedback, focusing specifically on correctness, coverage, and consistency validation.

Does the documentation review support resuming previous checks?▼

Yes, the documentation review supports resuming previous checks by using argument validation with optional --diff-base and --resume flags to handle output and strict size-budget requirements.

Why does documentation review require YAML frontmatter generation?▼

Documentation review requires YAML frontmatter generation to establish metadata structure for the Codex-driven accuracy critique, ensuring proper output handling and strict size-budget management during the verification process.