fix-errors

Fix ESLint and TypeScript errors across multi-package projects.

3|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/twikus/claude-configuration --skill fix-errors-twikus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/twikus/claude-configuration/tree/main/claude-code-config/skills/utils-fix-errors
Command: npx skills add https://github.com/twikus/claude-configuration --skill fix-errors-twikus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify and fix ESLint and TypeScript errors across a codebase by orchestrating parallel analysis and targeted fixes, reducing manual debugging time.

Core Features & Use Cases

  • Diagnose errors: Run lint and typecheck across all packages to surface issues.
  • Parallel remediation: Group errors by area and fix them concurrently to cut repair time.
  • Verification: Re-run diagnostics to ensure changes are valid and no new errors are introduced.

Quick Start

  1. Ensure pnpm is installed and dependencies are installed in your project.
  2. Run lint and typecheck to discover errors: pnpm run lint; pnpm run typecheck.
  3. Invoke the fix process to apply minimal, area-scoped fixes and verify results with a re-run of diagnostics.

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 across multiple packages at once?

To fix ESLint and TypeScript errors across multiple packages, this Skill runs lint and typecheck diagnostics in parallel, groups issues by area, and applies minimal targeted fixes concurrently to reduce manual debugging time.

What is the best way to automate typecheck and lint error remediation in a monorepo?

Automating typecheck and lint remediation in a monorepo involves running diagnostics across all packages, grouping errors by area, and applying fixes in parallel. This Skill orchestrates that workflow and verifies results by re-running diagnostics.

Do I need pnpm installed to run parallel lint and typecheck fixes?

Yes, you need pnpm installed and project dependencies set up before running parallel lint and typecheck fixes. The Skill uses npm/pnpm scripts to discover errors and apply area-scoped remediation across the codebase.

How does parallel error fixing work for ESLint and TypeScript issues?

Parallel error fixing works by running ESLint and TypeScript diagnostics concurrently across packages, grouping the resulting errors by area, and applying minimal fixes to each group simultaneously to cut repair time.

Can I use this automated fixing process for both lint and typecheck scripts?

Yes, you can use this automated fixing process for both lint and typecheck scripts. It runs pnpm lint and typecheck commands to surface issues, applies minimal area-scoped fixes, and re-runs diagnostics to ensure no new errors are introduced.

Why does ESLint and TypeScript error fixing group issues by area before applying changes?

Grouping ESLint and TypeScript errors by area before applying changes allows the fixing process to target issues concurrently and apply minimal, area-scoped fixes, which preserves functionality and cuts down repair time.