file-change-tracker

What problem does it solve?

It prevents you from losing track of what changed during a risky editing batch by creating explicit pre-change recovery snapshots and recording post-change results for only the paths you declare.

Core Features & Use Cases

• Path-scoped local Git recovery: Creates recovery points only for explicit target files/directories rather than snapshotting the whole repo.
• Pre/Post guarded sessions: Runs a mandatory pre before any file changes in a batch, then runs post afterward to commit only when new changes exist in the stored path set.
• User-visible rollback guidance: Surfaces recent commits/sessions and provides safe, path-scoped rollback instructions (diff preview, restore-to-pre, and revert-to-post options).

This is best when you are running model/tool workflows that generate or modify code, configs, docs, or artifacts into known locations and you want “undo with confidence” without replacing normal version control.

Quick Start

Run the file-change-tracker pre step once at the start of your change batch by passing a short reason and the exact target paths you will modify, then do the edits, and finally run post to record the outcome.