boba/jmove

feat: MVP — move files, rewrite imports, atomically

- core: gitignore-aware index (ignore crate), forward/reverse import graph,
  relative-specifier math, pure-data move plans
- apply: rewrite-first + rename-last with fsync, temp+rename, full rollback
  (incl. stale-plan detection before any write); unified diff for dry-run
- cli: mv + check commands, human output, --json envelope with stable error
  codes (SOURCE_NOT_FOUND, TARGET_EXISTS, ...) and hints; exit codes 0/1/2
- parser/core split into submodules to keep files <=250 lines
- tests: 37 unit + 10 e2e + 2 doctests; fixtures tests/typescript/{basic,normal,complex}
- docs: SKILL.md synced (no --force in Phase 1), EXAMPLES.md
- plan: AI/agent support done; Phase 1.5 = Java niche

2026-09-10 11:41:03 +02:00

1.9 KiB

Raw Blame History

jmove skill (for AI agents)

What this tool does

Moves or renames source files inside a project and updates every import statement referencing them. Never breaks imports. Supported: TypeScript, JavaScript; Java/Python/Go on the roadmap. Single binary, no LSP needed.

When to use

The user asks to move/rename/reorganize source files or packages.
You refactored a directory layout and imports now point at nothing.
You need to verify the project has no broken imports (check).

Commands

mv — move a file and rewrite its importers

jmove mv <source> <target> [--root DIR] [--dry-run] [--json]

Always run --dry-run first and confirm the change set looks right. Moving onto an existing path fails with TARGET_EXISTS — choose another target (Phase 1 has no overwrite mode).

check — find broken imports

jmove check [--root DIR] [--json]

Run after any move (or any edit) to validate project consistency.

Recommended agent workflow

jmove mv <src> <target> --dry-run --json — preview.
Inspect affected_files; if unexpected, abort and ask the user.
jmove mv <src> <target> --json — apply (atomic, rolls back on error).
jmove check --json — verify nothing is broken.

Output format (--json)

Every response: { "status": "ok" | "dry_run" | "error", "operation": "...", ... }. Errors carry a stable code (TARGET_EXISTS, SOURCE_NOT_FOUND, ...) and a hint describing the next action. On success, mv reports changed_files with line-level old/new import diffs and counters (moved, updated_imports).

Exit codes

0 — success
1 — operation failed (read --json error or stderr)
2 — check found broken imports

Rules of use

Never run mv without a prior --dry-run in the same session.
After every successful mv, run check; treat exit code 2 as a failed refactor.

1.9 KiB Raw Blame History