What problem does it solve? Inconsistent spelling, punctuation, and voice across design documents, test plans, and code comments make an engineering repository harder to read and review. This Skill defines the house style (American English, Oxford comma, lowercase simplyblock brand, third-person voice) and provides gate scripts that detect and auto-fix violations in Markdown, Go, Python, and YAML files. ## Core Features & Use Cases - Automated quality gates: Run quality-gate.sh to check American English spelling, punctuation, terminology, brand casing, prose errors, counterfactual phrasing, and identifier naming across the repository or only changed files. - Auto-fix support: Five checks (spelling, terminology, American English, punctuation, prose) rewrite their own findings in place with --fix, while the identifier gate reports renames to be done with refactoring tools. - Code-aware checking: In Go, Python, and YAML files only comments, docstrings, and declared names are checked, skipping code, tool directives, generated files, and vendored trees. - Use Case: Before handing back a change to operator/docs design documents, run the gates with --changed, capture the output to a file, clear every error, and record a verdict for each warning. ## Quick Start Ask the assistant to run the house-style quality gates on the changed files and resolve every reported error and warning.
