The gap between git commits is where the real chaos lives

Here is a scenario every developer knows:

You are working on a feature. You are making changes to 5 files. You are in the flow. You do not commit for hours.

Then something goes wrong. Maybe you overwrite something. Maybe you refactor too aggressively.

Git cannot help. You never committed.

This gap between commits is where most of my oh no moments happen. So I built a tool to fill it.

CodeFootprint runs on your Mac and continuously tracks file changes in any folder you select. Every edit, every deletion, every new file - all recorded with timestamps and full diffs.

Key features:

• Real-time file change detection
• Diff viewer for comparing versions
• Timeline of all changes
• Fully local - no cloud, no accounts
• Works with any file type: code, config, markdown, etc.

It is like having a DVR for your project files.

Available on the Mac App Store.

How do you deal with the commit gap?