doc-style-lint

What problem does it solve? Documentation often drifts away from style guide standards, accumulating passive voice, jargon, exclusionary terms, and untested code examples that confuse readers. This Skill provides a structured review process that catches these issues systematically before publication. ## Core Features & Use Cases - Style Rule Enforcement: Applies concrete rules for voice, tone, sentence length, headings, hyperlinks, code examples, and number formatting based on Microsoft and Google style guides. - Inclusive Language Detection: Flags terms like master/slave, whitelist/blacklist, and gendered language, suggesting approved replacements. - Structured Review Output: Produces a standardized report with readability metrics, issue counts, and a prioritized recommendations table. - Use Case: Before merging a new README or API guide, run this review to verify it passes Vale and markdownlint checks, uses active voice, contains no exclusionary terms, and has tested code examples. ## Quick Start Review the attached README.md against our documentation style guide and report any clarity or inclusive language issues.