move-a-file

Move or rename files and update references across source, docs, and configs.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/fengqiyu0317/assassyn --skill move-a-file-fengqiyu0317
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: move-a-file
Source: https://github.com/fengqiyu0317/assassyn/tree/main/assassyn-master/.claude/skills/move-a-file
Command: npx skills add https://github.com/fengqiyu0317/assassyn --skill move-a-file-fengqiyu0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moving or renaming files in a codebase without breaking references is error-prone; this skill automates updating all references in source code, documentation, and configuration files to ensure consistency.

Core Features & Use Cases

  • Path validation and automatic destination directory creation.
  • Reference discovery across the repository and safe execution via git mv.
  • Use Case: restructure a project by renaming a module file and updating imports, docs, and configs accordingly.

Quick Start

Provide the old file path, the new file path, and optional context, then trigger the move-a-file workflow to relocate the file and refresh all references.

Frequently Asked Questions about move-a-file

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

FAQPage Schema
How do I move a file in a codebase and update all references?

To move a file and update references, this skill uses ripgrep to discover all imports and configurations pointing to the old path, then executes a safe git mv operation while updating source code, documentation, and configuration files to ensure consistency. It returns a detailed report of all changes made.

What is the best way to rename a module file without breaking imports?

Renaming a module file without breaking imports requires path validation and reference discovery. This skill automatically checks if the old path exists and the new path is free, then updates references across multiple file types using ripgrep before safely executing the rename via git mv.

Does git mv automatically update references across documentation and configuration files?

Standard git mv does not update references in documentation and configuration files. This skill extends git mv by using ripgrep to discover and refresh all references across source code, docs, and configs, ensuring the codebase remains consistent after the file move.

Can I use this file moving skill for large software projects?

Yes, this file moving skill is applicable to software projects of any size. It enforces checks for path existence and non-existence, handles directory creation when needed, and safely updates references across the entire repository using ripgrep and git mv.

Why does renaming a file cause broken references in my project?

Renaming a file causes broken references because standard file operations do not update import paths or configurations. This skill solves the problem by discovering all references via ripgrep and updating them across source code, documentation, and configuration files before completing the git mv execution.

What are the limitations of automated file refactoring tools?

Automated file refactoring relies on accurate path validation and reference discovery. While this skill enforces existence checks and updates multiple file types, complex dynamic references or non-text configurations might not be fully captured by the ripgrep search, requiring manual verification of the generated change report.