local-version-control

Local git snapshots of agent workspace changes are created by staging files and committing locally without pushing. The skill blocks sensitive files like .env and large binaries, then requires a manual diff review to detect PII or secrets before finalizing the commit.

PII detection and secrets safety work by prompting a required manual inspection of the staged git diff before committing. This review step ensures sensitive information like tokens or credential file contents are not recorded in the local snapshot.

Scheduled cron snapshots can be used to track overnight agent operations. This skill applies to routine agent operation cycles by creating automated daily commits that capture workspace changes while respecting .gitignore and blocking credential files.

The best way to prepare for pre-destructive operations using version control is to create a reviewable local commit of the current workspace state. This stages changes while blocking large temp artifacts and requires a diff review to ensure no secrets are committed.

This local version control approach respects .gitignore and blocks large binaries or temp artifacts during the staging process. It specifically prevents risky commits by filtering out sensitive credential files and overly large binary data before the manual diff review.

Local version control forbids pushing commits automatically to remote to ensure human review of staged changes for sensitive information. This safety guardrail prevents accidental exposure of PII or secrets by requiring manual confirmation before any remote synchronization.