What does the 150% Lint Rule mean?

It refers to achieving 100% core requirements (zero errors/warnings) plus 50% enhancement goals like strict type safety, consistent style, and future-proofing.

Can this skill fix errors automatically?

Yes, it provides guidance for using auto-fix commands for ESLint and offers specific code patterns to manually resolve complex TypeScript and logic errors.

Does it support TypeScript compilation checks?

Absolutely. A key part of the protocol is running a full TypeScript compilation check to catch deep type errors that standard linters often miss.

How do I handle intentionally unused parameters in interfaces?

The skill follows industry standards by suggesting you prefix the parameter with an underscore or use specific ESLint-disable comments for documented exceptions.

Comprehensive Code Quality Validator

Name: Comprehensive Code Quality Validator
Author: MykhailoDmytriakha

byMykhailoDmytriakha

0•

Seguridad y Pruebas

Executes an intensive code quality suite combining ESLint, TypeScript compilation, and unused code detection to maintain high development standards.

The Comprehensive Code Quality Validator implements the '150% Lint Rule,' a rigorous protocol designed to move beyond basic syntax checking. It automates a multi-stage validation process that includes ESLint for style and logic, TypeScript for type safety, and deep scans for unused code or inefficient imports. By providing categorized error reporting and specific fix patterns, it helps developers resolve technical debt before it reaches production. This skill is ideal for pre-commit checks, ensuring that every code contribution is clean, consistent, and strictly typed.

Características Principales

010 GitHub stars

02Categorized error reporting by severity (Critical, High, Medium)

03Strict 'Quality Gate' protocol with multi-phase verification

04Enhanced detection of unused locals, parameters, and import hygiene

05Unified execution of ESLint, TypeScript compilation, and unused code checks

06Automated and manual fix guidance for complex linting and type issues

Casos de Uso

01Post-refactoring cleanup to identify orphaned types, unused exports, and broken dependencies

02Pre-commit validation to prevent broken code or lint violations from entering the main branch

03Standardizing codebase health and style consistency across collaborative team projects

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add mykhailodmytriakha/my-preacher-helper 61-validate-lint-150

For use in Claude.ai and ChatGPT

Download Skill