Zero Warnings Enforcer

What problem does it solve?

This Skill enforces a "Zero Warnings" policy, eliminating technical debt and improving code quality by strictly prohibiting ignored ESLint warnings, TypeScript errors, and weak types, leading to more reliable and maintainable software.

Core Features & Use Cases

• Broken Window Theory: Applies the principle that even small ignored issues lead to rapid code degradation, promoting immediate correction of all warnings and errors.
• Strict ESLint & TypeScript Rules: Provides guidance on configuring and adhering to strict linting and typing rules, including how to fix common issues like unused variables, any types, and unhandled promises.
• Quality Gates: Integrates pre-commit hooks (Husky, lint-staged) and CI/CD pipelines to enforce zero warnings/errors before code is merged or deployed.
• Use Case: During a code review, if a developer introduces a new ESLint warning or TypeScript error, this Skill guides them to identify the root cause and fix it properly, rather than suppressing the warning.

Quick Start

To ensure zero warnings, run yarn lint --max-warnings 0 and yarn tsc --noEmit before every commit. If a warning or error appears, identify its root cause and fix it, never disable the rule.