fix-errors

Detects and fixes TypeScript type errors, test failures, and lint issues until the project builds.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/kage1020/dotfiles --skill fix-errors-kage1020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/kage1020/dotfiles/tree/main/dot_codex/skills/fix-errors
Command: npx skills add https://github.com/kage1020/dotfiles --skill fix-errors-kage1020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

現在のプロジェクトのエラーを自動検出・修正する。

Core Features & Use Cases

  • TypeScript の型エラーを検出して修正する
  • テストの失敗を検出して修正する
  • Lint エラーを検出して修正する
  • 根本原因を特定して再発を防ぐための再現性のある修正を適用する

Quick Start

Scan the repository, detect TypeScript type errors, test failures, and lint issues, and apply fixes until the project builds.

Frequently Asked Questions about fix-errors

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

FAQPage Schema
How do I automatically fix TypeScript type errors and lint issues in my project?

To automatically fix TypeScript type errors and lint issues, you scan the repository, detect the errors using static analysis, apply fixes, and validate by running a full build to ensure project health.

Can I use automated tooling to fix test failures across JavaScript and TypeScript projects?

Yes, automated tooling can detect and fix test failures across typical JavaScript and TypeScript projects by identifying the root cause and applying reproducible fixes to prevent recurrence.

What is the best way to restore CI pipeline build health after a code change introduces errors?

The best way to restore CI pipeline build health is to detect TypeScript type errors, test failures, and lint issues, then apply automated fixes until the project builds successfully.

Does fixing lint errors and type errors automatically require a specific development environment?

Fixing lint errors and type errors automatically works across local development environments and CI pipelines, requiring static analysis, automated tooling, and validation by running a full build.

Why do my TypeScript type errors keep recurring after applying manual fixes?

TypeScript type errors recur when the root cause is not addressed; applying reproducible fixes based on static analysis identifies the underlying issue and prevents the error from reappearing.

What limitations should I expect when automatically fixing test failures and lint issues?

Limitations include the reliance on static analysis and automated tooling to identify issues, meaning complex or logic-based test failures may require manual intervention to achieve a reproducible fix.