Claude Code Plugins

Community-maintained marketplace

Feedback

TypeScript Build Checker

@gigi-f/babylon_fp
0
0

Check TypeScript compilation errors, run build commands, and validate the codebase. Use when the user mentions TypeScript errors, build issues, compilation problems, or wants to verify code integrity.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name TypeScript Build Checker
description Check TypeScript compilation errors, run build commands, and validate the codebase. Use when the user mentions TypeScript errors, build issues, compilation problems, or wants to verify code integrity.

TypeScript Build Checker

Check TypeScript compilation status and build the project.

Quick Start

Check for TypeScript errors

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npx tsc --noEmit

Build the project

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npm run build

Run development server

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npm run dev

Common Commands

Full type check with detailed output

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npx tsc --noEmit --pretty

Watch mode for continuous compilation

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npx tsc --watch --noEmit

Check specific file

cd /home/gianfiorenzo/Documents/Vs\ Code/babylon_fp
npx tsc --noEmit <filename>

Interpreting Results

  • Exit code 0: No errors, compilation successful
  • Exit code 1: Errors found, check output for details
  • Look for error patterns like:
    • error TS2345: Type mismatch
    • error TS2339: Property doesn't exist
    • error TS2322: Type not assignable
    • error TS2304: Cannot find name/type

Best Practices

  1. Always check TypeScript errors before committing code
  2. Fix errors from top to bottom (earlier errors may cause later ones)
  3. Use --noEmit flag to check without generating files
  4. Run full build after fixing errors to ensure no runtime issues