fix-errors

Diagnose and fix ESLint and TypeScript errors across monorepos.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/zuzu59/z-skills --skill fix-errors-zuzu59
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/zuzu59/z-skills/tree/main/skills/fix-errors
Command: npx skills add https://github.com/zuzu59/z-skills --skill fix-errors-zuzu59

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the detection and resolution of ESLint and TypeScript errors by dividing work into areas and processing them in parallel with specialized agents.

Core Features & Use Cases

  • Parallel error analysis: Breaks down lint/type-check errors into manageable areas.
  • Deterministic triage: Groups files by location to maximize fix efficiency.
  • Safe, incremental fixes: Applies minimal changes with validations and rechecks to maintain build health.
  • Use Case: A large monorepo with dozens of packages can be linted and fixed in parallel to reduce feedback loops.

Quick Start

Start the lint/type-check correction workflow on a project with existing ESLint and TypeScript setup.

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 monorepo?

To fix ESLint and TypeScript errors in parallel, this Skill groups files by area and dispatches snipper agents concurrently to resolve issues. It processes up to five files per area and re-runs diagnostics to verify that all applied fixes maintain build health.

What is the best way to automate lint and type-check corrections for large workspaces?

Automating lint and type-check corrections is best handled by dividing the workspace into manageable areas for parallel processing. This approach applies minimal changes incrementally and validates them, maximizing fix efficiency and reducing feedback loops in large workspaces.

Do I need existing lint and typecheck scripts to automate error resolution?

Yes, you need existing lint and typecheck scripts configured in your package.json to automate error resolution. The Skill relies on these scripts to discover errors and verify that the parallel fixes applied by its agents are successful.

Can I use parallel lint fixing for multi-package workspaces with many packages?

Yes, you can use parallel lint fixing for multi-package workspaces. It coordinates error discovery and area-based grouping to process multiple packages concurrently, which significantly reduces the time needed to resolve errors across large monorepos.

How does area-based grouping work when resolving TypeScript and ESLint errors?

Area-based grouping works by deterministically triaging TypeScript and ESLint errors and grouping files by their location. This grouping allows the Skill to dispatch parallel snipper agents that apply safe, incremental fixes to specific areas.

What are the limitations of parallel error fixing with snipper agents?

A limitation of parallel error fixing with snipper agents is the strict limit of five files processed per area. Additionally, it requires a pre-existing ESLint and TypeScript setup and cannot resolve errors in workspaces lacking these configured lint and typecheck scripts.