fix-errors

Group ESLint and TypeScript errors into areas and fix them in parallel.

Updated Aug 23, 2026

Search Tags:#automation #typescript #eslint #parallel #diagnostics #lint #tsc

Ready to run

npx skills add https://github.com/cedricfressin/claude-config --skill fix-errors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/cedricfressin/claude-config/tree/main/skills/utils-fix-errors
Command: npx skills add https://github.com/cedricfressin/claude-config --skill fix-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill fixes ESLint and TypeScript errors by breaking the work into areas and processing them parallel, reducing cycle time for large codebases.

Core Features & Use Cases

Area-based remediation: automatically group errors by directory or feature and assign up to five files per area.
Diagnostics & verification: run lint and type-check to capture errors, then re-run checks to confirm resolution.
Automation orchestration: discover commands from package.json (lint, typecheck/tsc, format) and drive parallel Snipper agents to apply fixes.

Quick Start

Use the fix-errors skill to scan your project for ESLint and TypeScript issues and start parallel fixes.

Frequently Asked Questions about fix-errors

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

FAQPage Schema

How do I fix ESLint and TypeScript errors in parallel across a large codebase?▼

Fix ESLint and TypeScript errors in parallel by grouping failures into directory-based areas of up to five files, launching parallel agents to apply remediation, and re-running checks to verify resolutions.

How does area-based remediation work for batch processing lint failures?▼

Area-based remediation groups lint and type-check failures by directory or feature, assigning up to five files per area to parallel snipper agents that apply fixes simultaneously to reduce cycle time.

Can I automate TypeScript type-check fixes without manually configuring the build commands?▼

Yes, you can automate TypeScript type-check fixes by discovering lint, typecheck, and format commands directly from your project's package.json, then driving parallel agents to apply the resolved corrections.

What is the best way to scale TSC and ESLint error resolution for multiple teams?▼

The best way to scale error resolution is processing areas in parallel with automated orchestration, allowing multiple teams to simultaneously fix grouped ESLint and TSC failures across the codebase.

Does this parallel error fixing approach verify code changes after applying remediation?▼

Yes, the approach verifies code changes by re-running lint and type-check commands after parallel agents apply fixes, confirming that the original errors are fully resolved before completing the cycle.