REPOGEO REPORT · LITE

f/git-rewrite-commits

Default branch master · commit 6a2cea3f · scanned 5/25/2026, 10:16:52 AM

GitHub: 1,410 stars · 56 forks

AI VISIBILITY SCORE

40 /100

Critical

Category recall

0 / 2

Not recommended in any query

Rule findings

2 pass · 0 warn · 0 fail

Objective metadata checks

AI knows your name

3 / 3

Direct prompts that named your repo

HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface f/git-rewrite-commits, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION

hightopics#1
Update repository topics for accurate categorization
Why:
CURRENT
```
git, pre-commit-hook
```
COPY-PASTE FIX
```
git, ai, git-history, commit-rewriter, ollama, gpt
```

highreadme#2

Add a clarifying sentence to the README's opening paragraph

Why:

CURRENT

Automatically rewrite your entire git commit history with better, conventional commit messages using AI. Perfect for cleaning up messy commit histories before open-sourcing projects or improving repository maintainability.

COPY-PASTE FIX

Automatically rewrite your entire git commit history with better, conventional commit messages using AI. Perfect for cleaning up messy commit histories before open-sourcing projects or improving repository maintainability. Unlike tools that enforce commit message formats or lint commits, this utility uses AI to *transform* your existing, messy commit history.

mediumreadme#3

Add a 'Comparison' section to the README

Why:

COPY-PASTE FIX

## Comparison to other Git tools
Many tools help with commit messages, but they serve different purposes:
- **Commitizen / commitlint / Husky:** These tools *enforce* commit message formats or run checks *before* a commit is made. They help you *create* good new commits.
- **git-rewrite-commits:** This tool uses AI to *rewrite and improve existing* commit messages and history *after* they've been made. It's for transforming messy history, not enforcing new standards.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall

0 / 2

0% of queries surface f/git-rewrite-commits

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

commitizen/cz-cli

Recommended in 2 of 2 queries

COMPETITOR LEADERBOARD

commitizen/cz-cli · recommended 2×
conventional-changelog/commitlint · recommended 2×
Git · recommended 1×
Sourcetree · recommended 1×
GitKraken · recommended 1×

CATEGORY QUERY
What tools can automatically rewrite my git commit history with AI assistance?
you: not recommended
AI recommended (in order):
1. Git
2. Sourcetree
3. GitKraken
4. GitHub Copilot
5. Commitizen (commitizen/cz-cli)
6. Commitlint (conventional-changelog/commitlint)
7. Semantic Release (semantic-release/semantic-release)
AI recommended 7 alternatives but never named f/git-rewrite-commits. This is the gap to close.
Show full AI answer
CATEGORY QUERY
How can I improve messy git commit messages for open-sourcing projects?
you: not recommended
AI recommended (in order):
1. Commitizen (commitizen/cz-cli)
2. Husky (typicode/husky)
3. pre-commit (pre-commit/pre-commit)
4. commitlint (conventional-changelog/commitlint)
5. git-commit-msg-linter
6. VS Code GitLens extension (gitkraken/vscode-gitlens)
AI recommended 6 alternatives but never named f/git-rewrite-commits. This is the gap to close.
Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

Metadata completeness
pass
README presence
pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

Compared to common alternatives in this category, what is the core differentiator of f/git-rewrite-commits?
pass
AI named f/git-rewrite-commits explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts f/git-rewrite-commits in production, what risks or prerequisites should they evaluate first?
pass
AI named f/git-rewrite-commits explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
In one sentence, what problem does the repo f/git-rewrite-commits solve, and who is the primary audience?
pass
AI named f/git-rewrite-commits explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of f/git-rewrite-commits. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/f/git-rewrite-commits.svg)](https://repogeo.com/en/r/f/git-rewrite-commits)

HTML

<a href="https://repogeo.com/en/r/f/git-rewrite-commits"><img src="https://repogeo.com/badge/f/git-rewrite-commits.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

f/git-rewrite-commits — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

Deep reports10 / month
Brand-free category queries5 vs 2 in Lite
Prioritized action items8 vs 3 in Lite