| name | move-files |
| description | Moves or renames any files/directories in a repo: preserves history, updates all references and build metadata, verifies no stale paths remain.
|
Move Files
Workflow
-
Preflight.
- Run
git status --short.
- Map each
source -> destination.
- Classify scope: simple same-module moves stay targeted; package, module, or
cross-module moves need broader inspection.
- Ask before ambiguous mappings, destination conflicts, or unclear semantic
package/module changes.
-
Search before moving.
- Search all old identifiers: paths, names, resource refs, doc links.
- For Gradle/module/source-set moves, check
settings.gradle.kts,
build.gradle.kts, and buildSrc.
- For Kotlin/Java, update package declarations only when package intent
changes.
-
Move safely.
- Always use
git mv for tracked files in the repo. If sandboxing blocks
it, request approval; do not use delete/create as a fallback.
- Use filesystem moves only for untracked/generated/out-of-git files.
- Create parent directories first.
- For case-only renames, move through a temporary name.
-
Repair references.
- Update all references: imports, build metadata, docs, resources, and scripts.
- Start search scope narrow: affected directory, then module, then repo-wide.
- Prefer precise edits; avoid broad replacements on generic names.
-
Verify.
- Re-run targeted searches for old tokens.
- Run
git status --short and confirm the delta matches the move.
- Run focused validation for moved files, or state what could not run.
-
Ensure the version is bumped.
Run the version-bumped skill so the branch carries a strictly greater
version.gradle.kts than the base ref before any ./gradlew build
(which can transitively publishToMavenLocal and overwrite
consumer-facing snapshots). The skill is a no-op if a bump already
happened earlier on the branch.
Repo Notes
Follow .agents/guidelines/project-structure-expectations.md for module/source-set/test moves.
Report
Return: Moved[], UpdatedRefs[], Verification[], Risks[].
