import-fixer

Repair broken import paths in TypeScript and JavaScript projects after file moves.

Updated Aug 27, 2026

Search Tags:#typescript #javascript #dependency-graph #code-maintenance #code-refactor #path-resolution #import-fixer

Ready to run

npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill import-fixer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: import-fixer
Source: https://github.com/emanuelrechsteiner/FairSplit/tree/main/.claude/skills/import-fixer
Command: npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill import-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix broken imports after file moves or renames by scanning for import errors, identifying broken paths, and updating all affected files.

Core Features & Use Cases

Identify and fix broken imports after file moves or renames.
Detect "Cannot find module" / "Module not found" errors and map to new paths.
Update all files that reference moved or renamed modules to restore a working codebase.

Quick Start

Run the fix after refactoring to automatically repair all broken import paths across the repository.

Frequently Asked Questions about import-fixer

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

FAQPage Schema

How do I fix broken import paths after moving files in a TypeScript project?▼

Fix broken import paths in TypeScript by scanning for 'Cannot find module' errors, mapping old imports to new file locations, and updating all affected files to restore compilation.

What's the best way to resolve 'Cannot find module' errors after a JavaScript file rename?▼

Resolve 'Cannot find module' errors by detecting the renamed JavaScript files, mapping the old import statements to their new locations, and automatically updating all dependent files.

Does import path resolution work for monorepos where multiple modules are relocated?▼

Import path resolution works for monorepos by scanning the repository for relocated or renamed modules and updating all cross-module dependencies to restore a working codebase.

How do I automatically update all files that reference moved modules during a refactor?▼

Automatically update dependent files by scanning the codebase for broken imports, identifying the new paths of moved modules, and rewriting the import statements across all affected files.

Why do I still have broken imports after renaming files in my JavaScript project?▼

Broken imports persist after renaming because standard compilers only flag missing modules without rewriting paths; you need to map the old imports to the new locations and update all references.

Can I repair broken imports across my entire repository at once?▼

Repair broken imports across the entire repository by running a scan that identifies all 'Module not found' errors and automatically updates every dependent file to point to the new module locations.