What problem does it solve? Reviewing pull requests and change sets for writing style violations is slow and inconsistent, especially when prose hides in code comments, error messages, UI labels, and test strings. This Skill audits every changed text surface against the Google developer documentation style guide and produces a structured findings report. ## Core Features & Use Cases - Full text-surface coverage: Audits docs, UI copy, errors, logs, comments, prompts, configuration descriptions, test strings, and terminology in identifiers, not just Markdown files. - Flexible scope resolution: Accepts a pull request, branch, commit range, patch, working tree, or named files, and resolves ambiguity before auditing. - Rule-grounded findings: Cites each finding with path and line, the exact current text, a suggested replacement, and the specific guide rule with a URL. - Use Case: Before merging a pull request that touches README files, CLI help text, and error messages, run the audit to catch non-inclusive terms, passive voice, and capitalization issues with concrete suggested fixes. ## Quick Start Audit the current working tree changes against the Google developer documentation style guide and report any style findings.
