Import Error Resolution Skill

Trace TypeScript and JavaScript module relationships to resolve import and export errors.

Updated Jan 15, 2026

Search Tags:#typescript #javascript #imports #circular dependencies #exports #module resolution

Ready to run

npx skills add https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5- --skill import-error-resolution-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Import Error Resolution Skill
Source: https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5-/tree/main/.claude/skills/import-error-resolution
Command: npx skills add https://github.com/Razaib-khan/Hackathon-2-phases-2-3-4-5- --skill import-error-resolution-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve TypeScript and JavaScript import/export failures, especially when modules cannot find expected named exports, default exports, or type-only symbols.

Core Features & Use Cases

Export Verification: Checks whether a requested symbol is actually exported by the source module.
Import Syntax Correction: Aligns import statements with the module’s export style, including default, named, and type-only imports.
Circular Dependency Triage: Helps identify and reduce import loops that can break module resolution.
Use Case: If a frontend build fails because a component imports a missing Task export, this Skill can trace the module chain, locate the mismatch, and suggest or apply a fix.

Quick Start

Ask the Skill to analyze the failing import, trace the module chain, and recommend the exact export or import change needed to resolve the error.

Frequently Asked Questions about Import Error Resolution Skill

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

FAQPage Schema

How do I fix TypeScript import errors when a named export is missing?▼

Trace the module chain to verify the requested symbol is actually exported by the source module, then align the import syntax with the module's export style to resolve the mismatch and fix the missing export error.

Why does my JavaScript build fail due to circular dependencies?▼

JavaScript builds fail due to circular dependencies when import loops break module resolution. You must identify and reduce these import loops to resolve the error without breaking existing runtime behavior.

How do I separate type-only imports in TypeScript to resolve module conflicts?▼

Separate type-only imports in TypeScript by correcting import statements to align with the module's export style, isolating type-only symbols from runtime values to resolve module resolution issues.

What is the best way to resolve default export conflicts in a JavaScript codebase?▼

The best way to resolve default export conflicts is by verifying the source module's exports and correcting the import syntax, ensuring default and named imports match the actual module export style to prevent build failures.

Does this approach work for module resolution issues in shared utility layers?▼

Yes, this approach works for module resolution issues in shared utility or API layers by tracing module relationships across shared code to locate mismatched exports and apply syntax corrections.