build-error-resolver_skill

Overview

This skill is a Build and TypeScript error resolution specialist that gets broken builds green quickly with minimal diffs. I focus on fixing compilation, type, import, dependency and configuration errors without making architectural changes. The goal is to restore a clean build fast and safely so development and deployment can proceed.

How this skill works

I run targeted diagnostics (npx tsc --noEmit, npm run build, eslint) to collect and categorize all errors. For each blocking error I apply the smallest safe change: add a missing type, fix an import, install a package, or adjust a config. After each change I re-run type checks and the build to ensure no new regressions. I document fixes concisely and keep changes minimal and scoped to the failing lines.

When to use it

• npm run build fails or exits non-zero
• npx tsc --noEmit reports type errors blocking progress
• Import or module resolution errors (Cannot find module)
• Configuration problems in tsconfig, webpack or Next.js
• Dependency/type declaration mismatches causing compile failures

Best practices

• Collect the full error set before fixing; prioritize blocking errors first
• Prefer adding a type annotation or null-check over broad refactors
• Use type assertions only as a last resort and document them
• Make one change per commit and re-run tsc after each change
• Avoid renaming or moving files unless required to fix resolution issues

Example use cases

• Fix implicit any errors by adding parameter types to functions
• Resolve missing module by correcting tsconfig paths or switching to relative imports
• Install missing packages and corresponding @types declarations to satisfy compiler
• Add optional properties or constraints to interfaces to match runtime data
• Adjust Next.js exports or split constants to avoid Fast Refresh full reloads