git.move

To move files in a Git repository and update references automatically, use a skill that runs `git mv` for the relocation and then searches all plaintext files to replace old paths with new ones. This ensures code and documentation consistency during refactoring.

The best way to relocate a directory in Git without breaking imports is to preserve history using `git mv` and simultaneously search the repository to replace old path references. This prevents broken links and import errors across the project.

Moving a file with `git mv` alone does not update import statements. A dedicated file relocation process is required to search through all plaintext files and replace old paths with new ones, ensuring all code and configuration references remain consistent.

You need to search and replace old paths after moving files in version control whenever you restructure a project or refactor modules. This process maintains consistency by updating all import statements and documentation references that point to the relocated files.

Yes, you can use this approach for project restructuring tasks. It handles both file and directory movement while preserving Git history, and automatically updates all occurrences of the moved path across the repository to maintain consistency.