import-refactor

Import refactoring automatically finds and updates import statements, string paths, and configuration references across Python, TypeScript, and JavaScript files when you move or rename modules. It verifies that all paths exist and imports resolve correctly, eliminating manual search-and-replace work and preventing broken imports.

Yes. The skill processes large refactors in batches, systematically updating imports by type while preserving your import style—absolute vs. relative paths. It handles documentation and config files too, reporting all changes made so you know exactly what was updated across your codebase.

The skill updates not just imports but also string-based paths in configuration files and documentation. It verifies each reference before and after the update, ensuring no broken links remain in configs, docs, or hardcoded path strings.

Yes. The skill supports Python, TypeScript, and JavaScript simultaneously, so you can refactor imports consistently across a polyglot codebase. It applies the same systematic verification and batch-processing logic to each language.

It validates that updated imports resolve and paths exist both before and after changes. This verification step catches mismatches early, drastically reducing post-refactoring bugs and ensuring code integrity before you run your application.

Map the old paths to new paths, then let the skill find all references in imports, strings, and configs. It updates them systematically by type, verifies resolution, and reports the total count of files and imports changed—typically saving hours of manual refactoring.