
gitreverse
Reverse engineer any repo into it's original prompt
The Lens
GitReverse takes any public GitHub repo and works backwards to a prompt that could have built it. Feed it a repository and it reads the structure, the README, and the metadata, then uses an LLM to write the kind of plain-English instruction you'd hand Cursor or Claude to recreate the project from scratch. It's a curiosity tool and a learning tool: a way to see how a finished codebase might be described as a single ask.
It's a web app you can use straight from gitreverse.com, and you bring your own LLM key, Grok, OpenRouter, Azure OpenAI, or Google AI. Self-hosting is possible since it's a Next.js app, with optional Supabase for saved history and shareable links. The setup is moderate if you run it yourself, trivial if you just use the hosted site.
Developers curious about prompt engineering, or anyone wanting to study how projects decompose into instructions, get a novel little tool here. It's not something you'll use daily, and the generated prompt is a reconstruction, not the actual history. Treat the output as a plausible recipe, not the truth of how the thing was really built.
The catch: the repo ships with no license, which technically means all rights reserved, so be careful before building on the code itself. The hosted tool is free to use but only as good as the model and key you bring. And reverse-engineering a prompt from a repo is inherently fuzzy, complex projects don't collapse into one clean instruction.
Free vs Self-Hosted vs Paid
fully freeFree tier: Free to use at gitreverse.com. You supply your own LLM API key.
Self-hosted: Run the Next.js app yourself, with optional Supabase for history. Free. Moderate setup.
Paid: None from the project. Your only cost is the LLM API usage you bring.
Free to use (bring your own LLM key). Note: the source ships with no license.
Get tools like this every Wednesday
One featured tool, three on the radar. No fluff.
About
- Owner
- Fili (User)
- Stars
- 1,065
- Forks
- 200
Explore Further
More tools in the directory
caveman
🪨 why use many token when few token do trick — Claude Code skill that cuts 65% of tokens by talking like caveman
72.2k ★oh-my-claudecode
Teams-first Multi-agent orchestration for Claude Code
36.4k ★awesome-copilot
Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.
35.0k ★