f/git-rewrite-commits — explained in plain English
Analysis updated 2026-05-18
Clean up a messy commit history into standardized conventional commit messages.
Auto-generate commit messages for every new commit via a git hook.
Rewrite commit history locally with Ollama to keep sensitive code private.
Preview rewritten commit messages in dry-run mode before applying changes.
| f/git-rewrite-commits | openkursar/hello-halo | yorgai/org2 | |
|---|---|---|---|
| Stars | 1,411 | 1,423 | 1,428 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | — | — | 2026-07-03 |
| Maintenance | — | — | Active |
| Setup difficulty | easy | easy | moderate |
| Complexity | 2/5 | 3/5 | 3/5 |
| Audience | developer | pm founder | developer |
Figures from each repo's GitHub metadata at analysis time.
Rewriting history requires a force-push and is unsafe on shared branches.
This tool uses AI to rewrite the commit messages in a git repository's history. Commit messages are the short descriptions developers write each time they save a change to a codebase. When those messages are vague or inconsistent, this tool can go back through all of them and replace them with cleaner, more descriptive ones following a standard format called conventional commits, which uses prefixes like "feat" or "fix" to categorize each change. You can run it without installing anything, just by typing a single command in a terminal. It supports OpenAI's models for the rewriting, or a local tool called Ollama that processes everything on your own machine without sending your code anywhere. For repositories containing sensitive code or credentials, the local option is recommended. The tool can also install hooks into git so that every new commit you make gets an AI-generated message automatically, either shown as a preview for you to accept or written directly into the commit editor. An important caution: rewriting commit history changes the internal identifiers for every commit and requires a force-push to update the remote copy of the repository. This is disruptive for shared branches where other people have already pulled the old commits. The README strongly recommends using this only on personal projects, feature branches before they are merged, or repositories you are about to make public for the first time. A dry-run mode lets you preview what the new messages would look like before anything is changed, and the tool always creates a backup branch before making any modifications.
A command-line tool that uses AI to rewrite messy git commit messages into clean, conventional-commit-style history, run once or automatically via a git hook.
Mainly TypeScript. The stack also includes TypeScript, Node.js, OpenAI API.
No license information was found in the material provided.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.