eslint-fixes

Name: eslint-fixes
Availability: InStock
Author: GAIA

Resolve ESLint violations and configuration conflicts with standardized refactoring patterns.

21|4|Updated Sep 4, 2024

Search Tags:#code quality #typescript #testing #linting #refactoring #eslint

Ready to run

npx skills add https://github.com/gaia-react/gaia --skill eslint-fixes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eslint-fixes
Source: https://github.com/gaia-react/gaia/tree/main/.claude/skills/eslint-fixes
Command: npx skills add https://github.com/gaia-react/gaia --skill eslint-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses recurring, non-trivial ESLint errors and configuration conflicts that often slow down development, ensuring code quality remains high without manual debugging.

Core Features & Use Cases

Pattern Resolution: Provides standardized fixes for common issues like no-void usage, circular prettier/canonical conflicts, and sonarjs deprecations.
Testing Best Practices: Enforces correct usage of testing-library screen queries and async event handling.
Use Case: When a build fails due to a canonical/export-specifier-newline conflict, this skill provides the exact refactoring pattern to resolve the issue while maintaining project standards.

Quick Start

Apply the eslint-fixes skill to resolve the current linting errors in the codebase by following the patterns defined for the specific rule violations.

Frequently Asked Questions about eslint-fixes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I resolve conflicting ESLint and Prettier formatting rules in a TypeScript project?▼

Fix circular ESLint and Prettier formatting conflicts by applying standardized refactoring patterns that enforce consistent code quality. This resolves rule-based deprecations and formatting discrepancies without requiring manual debugging.

What is the best way to fix testing-library async event handling and screen query anti-patterns?▼

Fix testing-library anti-patterns by enforcing correct usage of screen queries and async event handling. This provides standardized refactoring patterns to resolve common testing violations and maintain best practices.

How do I resolve SonarJS deprecation and no-void usage ESLint violations?▼

Resolve SonarJS deprecation and no-void usage violations by applying targeted code refactoring patterns. This addresses specific rule-based deprecations to clear linting errors while adhering to project-specific coding conventions.

Does this ESLint fix approach work with automated linting workflows?▼

Yes, this ESLint fix approach works with automated linting workflows by requiring adherence to project-specific coding conventions. It provides standardized refactoring patterns designed to integrate seamlessly into automated linting pipelines.

Why does my build fail due to a canonical and export-specifier-newline configuration conflict?▼

Builds fail due to canonical and export-specifier-newline conflicts caused by conflicting formatting rules. Apply the exact refactoring pattern provided to resolve the issue while maintaining project standards and passing linting checks.