Name: restic-home-backup
Problem solved: Provide reliable, encrypted, versioned backups of a Linux home directory with operational safety and repeatable recovery.
Inputs:
- Backup target type (local disk, sftp, s3, b2, etc.)
- Repository endpoint/path
- Secret handling method (env file or password file)
- Schedule preferences (daily backup, weekly prune, monthly check)
- Exclude patterns
Outputs:
- Installed and initialized restic repository
- Backup/prune/check scripts
- systemd service/timer units
- Validation evidence (snapshots + test restore)
- Short operator runbook
Safety boundaries (must never violate):
- Never print secrets or tokens in chat/log output.
- Never delete snapshots/repositories without explicit user confirmation.
- Never weaken permissions on credential files (chmod 600 minimum).
- Never claim backup success without checking command exit status and snapshot listing.
- Never apply system changes implicitly: require explicit --apply (or explicit user confirmation) before writing to /etc, /usr/local/bin, or /etc/systemd/system.

Workflow

Collect the minimum required values before changes:

If any critical value is missing, ask targeted questions.

Use these resources:

scripts/bootstrap_restic_home.sh to generate deterministic setup artifacts. It is PLAN-ONLY by default and requires explicit --apply for system changes. Optional flags control timer enablement, repository initialization, and initial backup run.
references/ops-checklist.md for day-2 operations and troubleshooting.

Create:

Run and verify:

Validate failure behavior:

Report exact failing command + short corrective action.

When user requests publication:

Keep publish actions explicit and auditable.

Response style requirements

Use descriptive language with concrete operational detail: