hns-oss-docs-verify

Validates Hugo documentation sites through build, locale-parity, and style gate checks.

1.2k|222|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill hns-oss-docs-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hns-oss-docs-verify
Source: https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/hns-oss-docs-verify
Command: npx skills add https://github.com/modu-ai/moai-adk --skill hns-oss-docs-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation sites with multiple locales and strict style rules accumulate silent drift: broken Hugo builds, missing translated pages, stale version badges, blacklisted URLs, and inconsistent section counts. This Skill provides a runnable exit gate that verifies all of these dimensions before any docs change is accepted.

Core Features & Use Cases

  • Build and sitemap verification: Runs a warning-free hugo --minify --gc build and confirms sitemap.xml exists.
  • Content and style gates: Greps for blacklisted domains, forbidden Mermaid LR/RL diagram directions, and body-text emoji that should use icon shortcodes.
  • 4-locale parity ratchet: Checks file-existence parity across ko/en/ja/zh pages and compares per-page section counts against a checked-in baseline, failing only on newly divergent pages.
  • Version-sync check: Ensures README badges and example version strings match the release version declared in hugo.toml.
  • Use Case: Before merging a docs update that touches Korean and English pages, run this gate to confirm the build is clean, no page lost locale parity, and all version displays match the current release.

Quick Start

Run the oss-docs verify gate on the docs-site directory and report any failing checks before handing results back to the orchestrator.

Frequently Asked Questions about hns-oss-docs-verify

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

FAQPage Schema
How do I verify a Hugo documentation site builds without warnings?

Run `hugo --minify --gc` inside the docs-site directory and require exit code 0 with no WARN or ERROR lines in the output. Then confirm `docs-site/public/sitemap.xml` exists to prove the build produced a complete site.

How to check translation parity across multiple locales in a docs site?

Compare file existence across locale directories so every ko page has en, ja, and zh counterparts, then compare per-page heading counts with grep and awk. A ratcheted baseline file records known divergences so the gate only fails on newly unbalanced pages.

What is a ratchet gate for documentation quality checks?

A ratchet gate compares current divergences against a checked-in baseline and fails only on new violations, rather than failing on all pre-existing debt. This keeps the gate enforceable from day one while ensuring the documented debt can only shrink over time.

Why does the Mermaid direction check reject LR and RL diagrams?

The style rule enforces top-down diagrams only, so any `flowchart LR`, `graph LR`, `flowchart RL`, or `graph RL` in content files fails the check. Use `flowchart TD` or `graph TB` instead to pass the style-compliance dimension.

Can this verification skill modify or commit documentation changes?

No, all checks are read-only grep, build, and file-existence commands. The skill never commits or pushes; it only reports pass/fail results per dimension back to the orchestrator for fixing and re-verification.