minervia-restore
Restore from Backup
List available backups and restore files to previous versions.
Why This Matters
Updates create backups automatically. If something goes wrong or you prefer your previous configuration, you can restore:
- All files from a specific backup
- Recover customizations that were overwritten
- Undo an update completely
Quick Start
List available backups:
bash ~/.minervia/bin/minervia-update.sh --list-backups
Restore from a specific backup:
bash ~/.minervia/bin/minervia-update.sh --restore 2026-01-18T10-30-00
What You'll See
Available backups:
2026-01-18T10-30-00 (15 files)
2026-01-15T14-22-33 (12 files)
To restore: ./minervia-update.sh --restore TIMESTAMP
Restore Process
- Select backup - Choose a timestamp from the list
- Preview files - See which files will be restored
- Confirm - Approve the restoration
- Restore - Files copied back to original locations
Important Notes
- Restoring overwrites current files with backup versions
- Consider creating a backup before restoring (run update first)
- Backups are stored in
~/.minervia/backups/ - Backups are kept forever (no auto-pruning)
Process for Claude
- List backups:
bash ~/.minervia/bin/minervia-update.sh --list-backups - If user specifies a timestamp, restore:
bash ~/.minervia/bin/minervia-update.sh --restore TIMESTAMP - If no backups exist, inform user that backups are created during updates
Success Criteria
- Backups listed or restored as requested
- User informed of restoration results
- Files restored to correct locations
More from aplaceforallmystuff/minervia-starter-kit
start-project
Create a new project with proper PARA structure. Ensures consistent project setup with completion criteria and status tracking.
3weekly-review
Weekly vault maintenance - process inbox, clean up daily notes, review project status. Keeps the system healthy.
2minervia-update
Update Minervia to the latest version while preserving your customizations. Creates backups, shows what's new, lets you choose how to handle conflicts. Use when you want the latest skills and improvements.
2log-to-daily
Capture conversation activity to today's daily note. Creates a continuous record of your work that Claude can reference in future sessions.
2systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. Requires root cause investigation before proposing fixes.
2verification-before-completion
Use when about to claim work is complete, fixed, or passing. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
2