Git For Me

Git for Me!

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
• How it works: four questions · parts · the search · verdicts · the live check · flags
• Example: PDF invoices
• Install (every agent, step by step: USAGE.md)
• What leaves your machine · Limits · Security
• Development · License

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:

| 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:

| Na