🩹 git-cure: An AI Doctor for Broken Git Repositories
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
What I Built
Git has a bad day. Your entire project shouldn't have to.
I built git-cure, a terminal-native Git diagnostics and recovery tool powered by Gemma 4. It helps developers recover from common Git problems without blindly copying commands from Stack Overflow or risking their uncommitted work.
Here's what it does:
- 🔍 Detects Git problems by inspecting repository status, reflog, commit history, and diffs.
- 🧠 AI-powered diagnosis uses Gemma 4 to analyze the repository state and suggest recovery steps.
- 🛡️ Safety snapshots preserve a recovery point before potentially destructive operations.
- ⚡ Guided recovery walks developers through fixes with interactive confirmation.
The goal is simple: help developers spend less time debugging Git disasters and more time building.
Who would pay for it? Freelancers, software developers, and small engineering teams who want to reduce downtime and avoid losing valuable work. It could be offered as a free open-source CLI with paid team features or premium support.
Demo
🎬 Live demo: [Add your demo video link here]
The project includes a working dashboard and backend, with a terminal-based demonstration of Git problem detection and recovery planning.
Code
🔗 GitHub Repository: https://github.com/Shravani-08/Hacktoberfest-B
The repository contains the project README and implementation for git-cure.
How I Built It
I built git-cure using a modular architecture combining Git diagnostics, AI-powered reasoning, and a safety-focused recovery workflow.
Tech stack:
- Gemma 4: Analyzes Git state and generates structured recovery recommendations.
- Node.js and TypeScript: Power the application services and backend.
- Socket.IO: Connects the backend with the real-time dashboard.
- React: Powers the interactive dashboard.
- Git CLI: Provides repository state, reflog, commit ancestry, and diff information.
Instead of asking developers to paste error messages into a chatbot, git-cure gathers repository information directly and uses it to produce context-aware recovery plans.
The safety engine creates a recovery snapshot before potentially destructive actions, while the interactive workflow keeps the developer in control.
Why Does Open Innovation Matter?
Git recovery involves sensitive information: source code, commit history, credentials, and unfinished work.
Open-weight models such as Gemma give developers more flexibility over how AI is deployed and integrated. They also make it easier to experiment with different models without redesigning the entire application around a single provider.
For git-cure, this matters because the AI should serve the developer's workflow, not lock the developer into one model or platform.
Open innovation also makes the project inspectable and extensible, allowing other developers to improve its diagnostics, contribute recovery strategies, and adapt it to their own workflows.
My Agent Session
Coming soon — I'll add my DevRelay agent session to show the development and debugging process behind git-cure.
Prize Categories
- Best Use of Gemma — for integrating Gemma 4 into Git diagnostics and recovery planning.
Top comments (0)