Odds are, most of what you want to build is already open source. Tell your AI
agent what you're making, and it finds it: which repos to use as they are,
which to adapt, and what's left for you to write. Every repo it names is real,
licensed for your use or flagged, and checked live.
It searches GitHub, GitLab and Codeberg. Works with Claude Code, Codex,
Copilot, Cursor, Gemini CLI, Cline, Devin, Open WebUI and any other MCP
client, or as an Agent Skill.
Its companion, Where My Hug At?,
does the same for Hugging Face models.
Contents
Try it
Add it to your agent (Claude Code here; every other option below):
claude mcp add --scope user git-for-me -- npx -y git-for-me
Then ask:
Git for me: a CLI that pulls the tables out of PDF invoices into a spreadsheet.
Your agent asks the few things it can't guess, splits the job into parts, and
comes back with a report like the one below, every
repo in it looked up moments before. It works for anything made of code:
Git for me: typo-tolerant search for the recipes on my Next.js site.
Git for me: a nightly job that backs up Postgres to S3 and tells Slack if it fails.
Git for me: a browser extension that saves recipes without the life story.
How it works
1. Four questions first
Ask for "a library that reads PDFs" and you get whatever is popular: in the
wrong language, under a license you can't ship, or abandoned years ago. So
before anything is named, four details come first. Your agent fills in what
the conversation or your codebase already says, and asks you the rest:
| What it asks | What that decides |
|---|
| Stack | What will it be written in?TypeScript on Node, Python 3.12, Rust | Which repos work as libraries, and which only beside your code |
| Platform | Where will it run?a web app, a CLI, a server, a phone app | What fits at all |
| License | What may the result be used for?commercial, open source, personal | Which licenses are allowed |
| Upkeep | How much code are you willing to own?needs to stay maintained, happy to own a fork | A maintained dependency, or a fork you keep up |
"Not sure yet" is a fine answer: the picks then cover the range.
2. Split the job
The agent breaks the need into parts, each with an input and an output (a PDF
→ its tables, tables → a spreadsheet). A part not worth a dependency (glue,
configuration, logic only your project has, a few lines) is marked WRITE:
a dependency for ten lines is a cost, not a feature.
3. Search for each part
What an agent remembers of open source is as old as its training, and misses
the long tail. So nothing is picked from memory. For every other part, the
agent writes a search (a topic, the stack's language, a few keywords, the job
in a few words), and it runs on three forges:
| Way | What it finds | Where |
|---|
| Most starred in the topic | What's proven | GitHub, GitLab, Codeberg |
| Rising in the topic | New repos gaining stars, including ones newer than the agent's training | GitHub |
| Names and descriptions holding each keyword | Tools that aren't tagged with the topic | GitHub, GitLab, Codeberg |
| README text | The long tail, by what the README says, like a web search | GitHub |
The ways take turns in the results, so a niche tool isn't buried under
whatever is most starred. Archived repos are left out everywhere, and so are
forks on GitHub and Codeberg. A stack that can use more than one language
(TypeScript can use JavaScript) searches them all.
4. Decide each part from what turned up
| Verdict | Meaning |
|---|
| USE | A repo the search found does this job as it is: depend on it, or run it beside your code. |
| ADAPT | One comes close: fork it or copy the part you need, license permitting. |
| BUILD | Nothing it found does the job: build it, reading the closest repos first. |
| WRITE | Not worth a dependency: write the code. |
The agent judges the results by what they say: description, stars, recent
activity, license, language. It may add a repo it knows that the search
missed, but that pick ranks after the search's, and the report marks it
from memory.
5. Check every pick
Every pick is looked up on its forge, live. Any that don't exist are dropped,
and the agent goes back to the search for others. The rest are flagged for
what would bite later, and that report is what you see. It also lists what
the search found that wasn't picked, so nothing it turned up is hidden. A
BUILD part whose search found repos says to check them before building one.
Under the hood it's an MCP server with three tools: git_for_me for the
method (steps 1, 2 and 4), git_for_me_search for step 3, and
git_for_me_verify for step 5.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
