reorganize-files

To reorganize a messy folder and fix broken paths, the Skill inventories scattered files, proposes a grouped layout, sweeps all imports and URL references, and verifies builds with typechecking. This ensures moved assets continue working at runtime.

The safest way to move web assets without breaking CSS url() references is to use an inventory-driven sweep that updates string-based paths, static imports, and metadata references atomically. Post-change verification catches any stale paths early.

File restructuring handles static imports and metadata path updates by performing a class-based reference sweep across configs, CSS, and OG tags. It updates every pointer atomically during the move to prevent silent runtime failures.

Yes, you can reorganize feature folders and preserve public URLs without breaking builds. The Skill proposes an approval-gated layout, updates embedded config paths, and enforces stale-segment grep checks to guarantee build safety.

A limitation of automated dependency scanning during directory restructuring is that it requires an approval gate before execution and needs build outputs like dist/ excluded. Users must explicitly approve any changes to public URLs to maintain reference integrity.

You need typecheck and stale-path grep after updating file references to verify that moved assets and configurations are actually correct. This post-change verification catches lingering broken paths and ensures build safety before the task completes.