Code that reads itself
Browse files with rendered READMEs, syntax highlighting, and image previews. Rewind any file through its history — even compare two versions of an image side by side.
Git for people who would rather keep building
GitHub, but friendlier. With undo built in.
The git tools GitHub never shipped: browse code, read history in plain English, and merge reviews with confidence. And when something breaks, undo it right where you spotted it — no mystery commands.
- Free on public projects
- Undo right in the history view
- Review changes before they land
git.tools/acme/website
Updatesmain
AI update broke sign-in
Mara · 14mUndoUpdated the homepage
Mara · 2hAdded contact form
Sam · 1dSet up the project
Sam · 3d
Pick an update. Put it back in one tap.
You choose access
Connect only the GitHub repos you want to use.
Review before anything lands
Safe fixes are prepared separately for you to inspect first.
Later work is protected
If a removal would clobber newer edits, git.tools stops instead.
The app
Everything you do on GitHub, minus the clunk.
One clean interface for your code, history, reviews, and issues — with recovery woven in where mistakes actually happen.
History in plain English
Commits grouped by day and described like a human would. Undo the latest change or roll back to any earlier point, right from the timeline.
Reviews that merge safely
See checks and merge conflicts before you decide. One click runs the preflight, squash-merges, and cleans up the branch for you.
Issues without the noise
File bugs, ideas, and questions with types that make sense, and discuss them without ever leaving your repo.
A trash can for your repo
Force-pushed away a day's work? Deleted the wrong branch? Recover lost commits and undelete branches straight from the Trash.
A command palette for everything
Jump to any file, action, or tool in a keystroke. No spelunking through menus to find what GitHub hid three clicks deep.
Start with what went wrong
Tell us the problem. Skip the Git lesson.
No command to memorize. Pick the situation that sounds like yours and follow a short, guided flow.
“Cursor changed too much”
Remove one bad update
Pick the update that broke things. git.tools checks whether it can remove it cleanly and stops rather than overwriting later edits.
“I need yesterday's working version”
Go back to a known-good point
Choose the moment your project still worked. git.tools prepares that older state separately for you to review.
“I have no idea what changed”
Compare it in plain English
Open an update or compare two versions without decoding a wall of Git terminology first.
Guided tools
And when things get weird, there's a tool for that.
Short, guided flows for the jobs Git makes scary. Each one checks before it acts — and when history has to move, it backs everything up first.
Time Travel
Roll a branch back to any past commit, via a review.
Rescue
Resurrect commits lost to a force-push or deleted branch.
Remove Commit
Surgically undo one bad update without touching the rest.
Squash
Combine messy WIP commits into one clean commit.
Combine
Merge two parallel feature branches safely.
Catch Up
Bring a fork up to date with the original project.
Backport
Apply one fix to multiple release branches at once.
Tag & Release
Cut a versioned release with generated notes.
Health Check
A one-click report card on your repo's health.
Detective
Bisect a regression down to the exact bad commit.
Save Points
Bookmark a known-good moment before doing something risky.
Safety you can actually see
No leap of faith required.
git.tools does the risky reasoning before it offers the button. You still see the plan and choose whether anything lands.
It checks newer work first
Before removing an update, git.tools checks whether its files changed again. If newer work would be lost, it stops and tells you why.
The fix starts separately
When something needs recovering, you get a review to look over first. Nothing gets silently rewritten.
You decide what lands
Review the proposed files and approve the fix when it looks right. Close it and your current version stays unchanged.
Safety check
Safe to remove this update
2 touched files checked
No newer edits will be overwritten
Current version stays unchanged
GitHub review #42 readycurrent version unchanged
Getting started
From “oh shit” to a reviewable fix.
1
Connect your project
Sign in with GitHub and choose the projects you want git.tools to access.
2
Point at the problem
Open the update or version that matters and choose the plain-English action that matches your situation.
3
Review the proposed fix
git.tools runs its safety checks and prepares a separate GitHub review. You decide whether to approve it.
Pricing
Start free. Upgrade for private projects.
Two plans, no trial maze: Free for public projects and Pro for everything else.
Free
$0forever
Use git.tools on public GitHub projects.
- All available tools on public repos
- Guided previews and safety checks
- No payment details needed
Pro
Pro$7/month
Or $70/year. Bring your private projects too.
- Private repos on your GitHub account
- Every available git.tools workflow
- Manage or cancel anytime
Prices in USD. Upgrade, switch billing periods, or cancel from the app.
Before you connect
Fair questions. Straight answers.
Does git.tools replace github.com?+
For day-to-day work, yes. Browsing code, reading history, reviewing and merging pull requests, and tracking issues all happen in git.tools. Your data stays on GitHub — git.tools is a friendlier interface on top of it, with recovery tools woven in.
Will git.tools change my current branch immediately?+
Safe recovery flows such as Remove Commit and Time Travel prepare their work on a separate branch and open a pull request. Your current branch changes only if you review and merge it.
What if newer work touched the same files?+
Remove Commit stops rather than overwriting those later edits. It tells you which files conflict so you can choose a safer path.
Which repositories can git.tools see?+
git.tools sees the repositories your GitHub account can access. You can revoke the authorization at any time from your GitHub settings.
Can it fix changes I have not pushed to GitHub?+
No. git.tools works with project history already on GitHub. Unpushed changes remain in your editor or local Git client.
gittools
The next time AI breaks something, skip the terminal panic.
Connect GitHub, choose a project, and see its updates in plain English. Public projects are free and you review proposed fixes before they land.
