fix-imports

Detect and auto-fix malformed, duplicate, and missing imports in TypeScript and Vue files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Vulnetix/vdb-api --skill fix-imports
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-imports
Source: https://github.com/Vulnetix/vdb-api/tree/main/.claude/skills/fix-imports
Command: npx skills add https://github.com/Vulnetix/vdb-api --skill fix-imports

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically detects and corrects malformed, duplicate, and missing import statements in TypeScript and Vue files, ensuring code integrity and preventing runtime errors.

Core Features & Use Cases

  • Detects and fixes malformed imports: Removes extra semicolons or quotes.
  • Identifies and merges duplicate imports: Consolidates multiple imports of the same module.
  • Adds missing imports: Ensures all used symbols are properly imported.
  • Enforces backend extension rules: Verifies .ts extensions for relative imports in functions/.
  • Use Case: Refactor a large codebase by automatically cleaning up all import statements, improving maintainability and reducing potential bugs.

Quick Start

Run the fix-imports skill to clean up imports in the src directory.

Frequently Asked Questions about fix-imports

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

FAQPage Schema
How do I fix malformed and missing TypeScript imports in my project?

To fix duplicate and missing TypeScript imports, use an automated refactoring process to detect and consolidate duplicate module statements, add missing symbols, and correct syntax errors across your codebase scope.

Can I automatically enforce backend extension rules for relative imports in Vue files?

Yes, you can enforce backend extension rules by verifying that relative imports within specific directories like functions/ include the required .ts file extensions, ensuring your Vue and TypeScript files meet project conventions.

What causes duplicate import statements in a TypeScript codebase and how do I clean them up?

Duplicate import statements occur when the same module is imported multiple times; you can clean them up by automatically identifying and consolidating these duplicates into single statements during a codebase refactoring scope.

Does auto-fixing import statements run a build dry-run to validate code changes?

Yes, auto-fixing import statements validates code changes by re-scanning the codebase and running build or deploy dry-runs to ensure the corrected imports do not introduce new compilation errors.

What are the limitations of automated import refactoring for large codebases?

Automated import refactoring limitations include relying on a specified codebase scope for detection and requiring build dry-runs afterward to validate that fixes for missing or malformed statements do not break existing project conventions.