What problem does it solve? Repositories often use lint, validate, format, test, and audit as interchangeable script names, creating confusion about what each command actually does and whether it mutates files. This Skill defines a consistent taxonomy so every quality-check command has a predictable, meaningful name. ## Core Features & Use Cases - Naming Taxonomy: Defines distinct meanings for check, lint, validate, format, test, and audit, with check as the umbrella non-mutating quality gate. - Mutating Command Rules: Enforces explicit :fix, :write, and :update suffixes so non-mutating gates never modify files. - Decision Rules & Baseline: Provides ordered decision questions, a recommended package.json scripts baseline, and anti-pattern examples for JavaScript, TypeScript, Astro, and Markdown repositories. - Use Case: When setting up a new repository or auditing an existing package.json, apply this taxonomy to rename scripts like a mislabeled validate running ESLint into lint:code, and compose a top-level check command. ## Quick Start Ask the AI to audit the package.json scripts in this repository and rename them according to the quality gate naming conventions.
