skill-doc-diff

To perform a structured Qt documentation diff review, apply a standardized template that enforces consistent categorization, validation fields, and formal justification for audit-ready traceability across documentation changes.

The best way to ensure consistency when reviewing Qt doc changes is using a fixed output schema with fields for category, keywords, dependencies, and toxicity checks, capturing exemptions and rationale for formal decisions.

A validation template helps with documentation QA checklists by automating the creation of reviewable assessments, enforcing fixed output schemas for category and warning fields, and providing audit-ready notes to capture rationale.

This structured review template is specifically applied to Qt Doc Team diff workflows where diff-like changes require consistent categorization and formal justification, making it less suitable for non-Qt documentation environments.

Required fields in a Qt doc diff review output include name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity check, alongside safety considerations and audit notes.