What problem does it solve? Restore scripts for dotfiles only truly run on a brand-new machine, so testing them on an existing machine silently skips the failure paths (e.g., ln failing with File exists). This Skill runs the full backup-to-restore flow inside a fake HOME created with mktemp -d, proving the restore actually works on a fresh machine without touching the real home directory. ## Core Features & Use Cases - End-to-end restore verification: Executes scripts/verify_restore.sh, which checks script syntax, fresh-machine restore, shell startup with aliases, idempotency across two runs, salvage behavior for existing files, missing-archive fallback, archive contents (AES-256, socket exclusion), pre-commit credential blocking, and template consistency. - Safe isolation: Never touches the real ~; the fake HOME is deleted afterward, and only read and staging operations are performed on the real repository. - Actionable failure reports: Failures print expected versus actual values so you can fix the script and re-run until all checks pass. - Use Case: After editing scripts/restore_dotfiles.sh or changing the public/private directory layout, run the verification to confirm a new machine could still be restored before committing. ## Quick Start Ask the assistant to verify that the dotfiles restore works on a fresh machine by running the verify-restore check.
