agent-build-error-resolver

Diagnose and fix TypeScript and build errors with minimal code changes.

5|15|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-build-error-resolver-clfigueiredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-build-error-resolver
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/agent-build-error-resolver
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill agent-build-error-resolver-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Build failures and TypeScript type errors block development and deployment. This Skill provides a structured operational procedure for diagnosing compilation errors, type mismatches, import issues, and configuration problems, then fixing them with the smallest possible diffs so the build goes green quickly. ## Core Features & Use Cases - TypeScript Error Resolution: Fixes type inference issues, missing annotations, null/undefined errors, and generic constraint problems using npx tsc --noEmit diagnostics. - Build and Dependency Fixing: Resolves module resolution failures, missing packages, version conflicts, and tsconfig/webpack/Next.js configuration errors. - Minimal-Diff Discipline: Applies only the smallest change needed per error, with explicit rules against refactoring, architecture changes, or unrelated edits. - Use Case: Your Next.js project fails npm run build with 12 type errors after a dependency update. Activate this Skill to triage errors by priority, apply targeted fixes, and verify the build passes. ## Quick Start Ask the agent to run the build-error-resolver skill on your project, paste the failing build or tsc output, and request minimal fixes until the build passes.

Frequently Asked Questions about agent-build-error-resolver

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

FAQPage Schema
How do I fix TypeScript build errors quickly?▼

Run npx tsc --noEmit --pretty to collect all type errors, categorize them by kind (inference, imports, config, dependencies), then apply the minimal fix for each such as a type annotation or null check. Rerun tsc after each fix until it exits with code 0.

How to fix 'Object is possibly undefined' TypeScript error?▼

Fix it with optional chaining (?.) or an explicit null check before accessing the property. This is one of the common minimal fixes the procedure applies without changing surrounding logic.

What does 'Cannot find module' mean in TypeScript?▼

It means the compiler cannot resolve an import path. Check tsconfig path mappings, verify the package is installed, or correct the import path. Reinstalling dependencies can also resolve version-related resolution failures.

When should I not use a build error fixing approach?▼

Avoid it when the code needs refactoring, architectural redesign, new features, failing test repair, or security review. Those scenarios call for dedicated refactoring, planning, testing, or security workflows instead of minimal error fixes.

Why does my build still fail after fixing type errors?▼

Stale caches or broken dependencies often cause persistent failures. Try clearing .next and node_modules/.cache, or reinstall node_modules and package-lock.json, then rerun npm run build to verify.