LLM Skills
~/catalogue/debugging et maintenance//build-fix.prompt

Résolution des erreurs de construction

/build-fix.prompt

Examinez systématiquement l'erreur. Corrigez les causes profondes - ne supprimez pas les avertissements et ne sautez pas les contrôles.

affaan-maffaan-m
252.2k
4 juin 2026
MIT
// contenu du skill

agent: agent

description: Systematically diagnose and fix build errors, type errors, or failing CI


Build Error Resolution

Work through the error systematically. Fix root causes — do not suppress warnings or skip checks.

Process

1. Capture the full error

Paste or describe the complete error output (not just the last line). Include:

  • Error message and stack trace
  • File and line number if shown
  • Build tool and command that failed

2. Categorize the error

CategorySignals
Type errorType X is not assignable to Y, Property does not exist
Import/moduleCannot find module, does not provide an export
SyntaxUnexpected token, Expected ;
Dependencypeer dep conflict, missing package, version mismatch
Environmentcommand not found, ENOENT, missing env var
Test failureexpected X but received Y, assertion failure
LintESLint, no-unused-vars, no-console

3. Fix strategy

  • Type errors — fix the type, do not cast to any or unknown unless truly unavoidable.
  • Import errors — verify the export exists; check for circular dependencies.
  • Dependency errors — update lockfile, reconcile peer dep versions, do not delete node_modules as a first step.
  • Test failures — fix the implementation if behavior is wrong; fix the test only if the test itself is incorrect.
  • Lint errors — fix the code, do not add // eslint-disable unless the rule is genuinely inapplicable and you document why.

4. Verify the fix

After applying a fix, run the build/test command again. Confirm the specific error is resolved and no new errors were introduced.

5. Check for related issues

A single root cause often produces multiple error messages. After fixing, scan for similar patterns elsewhere in the codebase.

Rules

  • Never use --no-verify to skip hooks.
  • Never suppress type errors with @ts-ignore without a comment explaining why.
  • Never delete lock files without understanding why they are conflicting.
// source originale publique
affaan-m/ECC
/.github/prompts/build-fix.prompt.md
Licence : MIT
Projet indépendant, non affilié à Anthropic. Ce skill reste la propriété de son auteur original.
// installer ce skill
Collez cette commande dans votre terminal à la racine de votre projet :
mkdir -p .claude/commands && curl -o ".claude/commands/build-fix.prompt.md" "https://raw.githubusercontent.com/affaan-m/ECC/main/.github/prompts/build-fix.prompt.md"
Ensuite dans Claude Code, tapez /build-fix.prompt pour l'activer.
open_in_newVoir la source originale
// sauvegarder
Sauvegarde disponible après connexion.
loginSe connecter pour sauvegarder
// informations
Créateuraffaan-m
Étoiles 252.2k
LicenceMIT
Mis à jour4 juin 2026
Format.md
AccèsGratuit
// similaires

Skills Debugging et maintenance

Voir toutarrow_forward