docs-check-zh-cn

Check OpenHarmony API documentation for template compliance and consistency against d.ts declarations.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill docs-check-zh-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-check-zh-cn
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/oh-docs-check-zh-cn
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill docs-check-zh-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Prevent OpenHarmony API documentation from drifting away from required templates or the actual API definitions by automatically finding template violations, missing fields (like system interface/error-code sections), and link/consistency issues.

Core Features & Use Cases

  • Template compliance & field coverage: Verifies that public/system API docs, error-code docs, and interface documentation include required labeled fields (e.g., system interface, permissions, model constraints) and match expected structures.
  • Script-assisted consistency checking: Runs automated checks first via the bundled Python script to catch high-confidence mismatches between d.ts tags and Markdown documentation fields.
  • Error-code doc auditing: Ensures error-code documents include required blocks and that the error-code coverage is consistent with declared @throws codes in d.ts.
  • Implementation alignment & manual follow-up: Helps identify documentation gaps that automation can’t reliably validate, then produces an issues-only Markdown report with locations and suggested fixes.

Quick Start

Run this skill to check API doc consistency for the repository’s docs and interface definitions, focusing on issues only.

Frequently Asked Questions about docs-check-zh-cn

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

FAQPage Schema
How do I check OpenHarmony API documentation for consistency against d.ts declarations?

Check OpenHarmony API documentation consistency by running the bundled Python script to automatically detect mismatches between d.ts tags and Markdown fields. The script executes first to catch high-confidence template violations, missing permissions, and link issues before manual semantic review.

What does an OpenHarmony API documentation template compliance audit include?

A template compliance audit verifies that public and system API docs include required labeled fields like permissions, model constraints, and system interface sections. It checks Markdown structures against expected templates and ensures error-code documents align with declared @throws codes in d.ts files.

Why are my OpenHarmony error-code docs failing consistency checks with d.ts declarations?

Error-code docs fail consistency checks when required documentation blocks are missing or error-code coverage does not match the declared @throws codes in the d.ts interface declarations. The auditing script identifies these mismatches and reports them alongside template field coverage gaps.

How do I audit OpenHarmony interface documentation for missing system interface sections?

Audit interface documentation by executing the consistency checking script to locate missing required fields like system interface sections, permissions, and model constraints. The script scans /docs and /interface paths to find template violations and produces an issues-only Markdown report with locations and suggested fixes.

Can automated scripts catch all OpenHarmony API documentation gaps during a consistency review?

Automated scripts cannot catch all documentation gaps reliably. The consistency checker runs automated checks first for high-confidence d.ts and Markdown mismatches, but manual semantic review is required to identify implementation alignment gaps that automation misses before producing the final issues report.