Most Git workflows still make you stop what you are doing to create a checkpoint.

GitSave turns a normal save into a local commit, so you can keep a fine-grained history without bouncing out to the terminal every few minutes.

That is either extremely convenient or slightly unhinged, depending on your relationship with commit history.

For the right workflow, it is great.

Install from the VS Code Marketplace

Sometimes you want lots of small local checkpoints.

Maybe you are drafting. Maybe you are experimenting. Maybe you are about to refactor something questionable and would like a breadcrumb trail back to sanity.

Manual git add and git commit is not hard, but it is enough friction that people skip it.

GitSave removes that little interruption.

Save file in VS Code
  -> GitSave stages that file
  -> GitSave creates a local commit
  -> you keep working

Most Git tooling assumes commits are explicit moments.

GitSave treats them more like lightweight checkpoints for personal workflows.

It is less "craft the perfect commit message" and more "please let me preserve this version before I break something interesting."

When enabled, GitSave can:

• stage the current file with Git
• create a local commit using an automatic timestamp-based message
• expose a terminal view for debugging commit behavior
• support settings for defaults and notifications

It works inside repositories already opened in VS Code and is intended for workflows where automatic local commits are acceptable.

GitSave is a better fit for:

• developers who want more granular local history
• writers and coders who make many small edits
• personal projects where frequent local checkpoints are useful

It is not really aimed at pristine shared history straight out of the box, and that is okay.

1. Install GitSave from the Visual Studio Code Marketplace.
2. Open a folder that is already a Git repository.
3. Run GitSave: Enable from the command palette.
4. Save a file.

Once enabled, the save action triggers the extension's staging and local commit workflow for that file.

GitSave shines in workflows like:

• drafting documentation with automatic revision history
• saving incremental code experiments
• keeping a checkpoint trail before squashing or cleaning up later

It is a small tool, but it solves a very real "I wish I had committed that" problem.

GitSave expects Git to be available locally.

It creates local commits only. It does not automatically push to a remote.

And because it creates commits automatically, it is best used in repos where highly granular local history is intentional rather than accidental.

No. Its core workflow is local staging and local commit creation inside the current repository.

Probably not.

It is best for workflows where lots of automatic local checkpoints are actually helpful.

• Visual Studio Marketplace: Anthonykung.gitsave
• Source code: Anthonykung/GitSave

Sometimes the best productivity tool is the one that quietly saves you from your future self.

GitSave is basically that, but with Git.