move-code
Skill904 starsChanged 4 days agoMITView on GitHub
Move or rename TypeScript files, folders, or top-level declarations and leave every reference to them correct. Use when a change moves or renames source files, moves a function, type, class or const from one file to another, or renames one, such as gathering code into a context folder.
In this repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- ios/CLAUDE.mdCLAUDE.md
- rome_apps/CLAUDE.mdCLAUDE.md
- add-oauth-integrationSkill
- babysit-prSkill
- color-auditSkill
- dddSkill
- file-issueSkill
- imports-ofSkill
- loop-northstarSkill
- loop-reconcileSkill
- release-rome-imageSkill
- respond-to-reviewSkill
- secondary-text-auditSkill
- todos-to-github-projectSkill
- ux-semantics-auditSkill
- validate-oauth-integrationSkill
The file
Files
Move code
Run every move through pnpm move-files <from>:<to> ... (scripts/move-files.ts), never through git mv and hand edits. Give all the moves of one change in one call, and list only the source files: their tests follow them. The tool rewrites imports, mock paths, Markdown links, and paths in docs and comments that name a moved file, then formats what it touched.
Move a top-level declaration between files with pnpm move-symbol <from> <to> <name> ..., and rename one with pnpm rename-symbol <file> <old> <new>, never by hand. Both drive TypeScript's own refactors (scripts/ts-service.ts), so they reach the files the package's tsconfig includes. rename-symbol refuses a new name that already means something where the old one is written. move-symbol ends with a list to check by hand: mocks of the old file, namespace re-exports of it, and an import cycle between the two files. Clear unused imports with Biome: biome lint --only=correctness/noUnusedImports --write --unsafe <paths>.
You own what move-files lists at the end: lines that still name an old path, which are paths built by hand in code, configs and bundler inputs. Fix each one or confirm it names something else. A path assembled from folder names, such as join(dir, "actions"), is not listed, so search for the old folder names yourself.
The move is done when pnpm typecheck and pnpm lint:imports pass, every line move-symbol listed is fixed or confirmed, the tests of every moved file pass, and git shows each moved file as a rename whose only edits are paths. When the tool rewrites a reference wrongly, or misses one it could find mechanically, fix the tool as well as the output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

