config-file-versioning

This skill auto-versions local config files by setting up a per-domain git repository with a separate gitdir pointer, an OS-level watcher, and an auto-commit workflow that stages and records changes only when file content actually changes.

Automatic git commits for dotfiles can be set up using OS-level watchers like macOS launchd or Linux systemd. The workflow includes a safety throttle to prevent excessive commits and only triggers when actual content changes are detected.

Tracking dotfile changes without committing temporary runtime files is best achieved using a whitelist-based .gitignore. This ensures that only the actual config files are versioned, keeping the git history focused and clean.

Yes, git histories can be isolated by enforcing a per-domain separate git repository for each protected config domain. This approach uses a separate git-dir pointer to ensure clean, independent histories and isolated enablement.

A proper config file watcher should ignore mere mtime updates and only record commits when detected content actually changes. This prevents cluttering the version history with empty or irrelevant commits during silent overwrites.

No, manual git repository management is not needed to rollback local config changes. The auto-commit workflow handles staging and committing automatically, allowing you to instantly rollback to previous configurations when tools or installers overwrite files.