document-review

Lint HOTL documents and run AI-based rubric reviews with outcome gates.

25|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/yimwoo/hotl-plugin --skill document-review-yimwoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-review
Source: https://github.com/yimwoo/hotl-plugin/tree/main/skills/document-review
Command: npx skills add https://github.com/yimwoo/hotl-plugin --skill document-review-yimwoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated document assessment and linting for HOTL docs, plus AI-based reviews for non-HOTL documents.

Core Features & Use Cases

  • Structural lint for HOTL documents: validates design contracts, governance, and verification artifacts before AI review.
  • AI-driven review for non-HOTL content: applies a generic rubric to a wide range of documents.
  • Input classification and gated execution: decides whether to run lint first and uses deterministic steps to surface issues ahead of execution.

Quick Start

To start, feed a HOTL document into the Document Review Skill to perform lint then AI review.

Frequently Asked Questions about document-review

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

FAQPage Schema
How do I automate lint and AI rubric review for HOTL design docs?

Automated document review applies a deterministic lint phase via scripts/document-lint.sh to validate HOTL design contracts, followed by AI-driven rubric evaluation to enforce PASS, REVISE, or HUMAN_OVERRIDE_REQUIRED outcome gates.

What is the best way to run a structural lint check on workflow files before AI review?

Structural lint for HOTL workflow files validates governance and verification artifacts before AI review by using deterministic steps to surface issues, ensuring design contracts meet compliance before executing the AI-driven rubric evaluation.

Can I use AI rubric review for non-HOTL documents without running the deterministic lint?

AI-driven review for non-HOTL documents applies a generic rubric to evaluate content without requiring the deterministic lint phase, using input classification to decide whether to run lint first based on the document type.

Does document review support gated execution to block invalid workflow files?

Gated execution enforces outcome gates of PASS, REVISE, or HUMAN_OVERRIDE_REQUIRED for AI review, using input classification and deterministic lint steps to block invalid workflow files from proceeding without required revisions or human intervention.

When do I need HUMAN_OVERRIDE_REQUIRED status during AI-based document review?

HUMAN_OVERRIDE_REQUIRED status is enforced during AI-based document review when the rubric evaluation determines that automated PASS or REVISE outcomes are insufficient, requiring manual intervention to resolve complex validation issues in HOTL documentation.

What limitations exist when applying automated lint to non-HOTL governance artifacts?

Automated lint specifically validates HOTL design contracts, governance, and verification artifacts, meaning non-HOTL documents bypass the deterministic lint phase and rely solely on AI-driven generic rubric review without structural validation.