How it works

Paste a URL. Read the doc.

No config, no access tokens for public code, no 12-step onboarding. Five steps under the hood — the first two are yours, the rest are ours.

// gitpitcher.input

github.com/owner/repoGenerate →

The same input drives every mode

Or skip the form entirely — swap github.com for gitpitcher.com on any repo URL.

End to end

What actually happens when you hit generate.

Paste a GitHub URL

Owner/repo shorthand works. Public repos need no setup. For private repos on Pro, install the GitHub App once and every subsequent run is one click.

Pick a mode

Repo Read, Audit, or Build Pack. Same repo context, guided next step — understand the opportunity, inspect the gaps, then generate the agent-ready build plan.

Read the repo

We pull README, manifests, file tree and release signal — enough to reason about the product commercially, without cloning the whole thing.

Stream the doc

Each section renders live as the model writes it. You see the artifact appear top-down — decision first, then supporting detail, then the next move.

Refine, export, or rebuild

Save revisions, ask for deeper cuts, export to Markdown or GitHub Issues, or move into Build Pack when the next step is implementation.

Ground rules

What we promise and what we don't.

Your input isn't training data

Repo URLs and generated outputs are never sold, never used to train models, and you can delete every pitch from your dashboard at any time.

Public repos stay public

We only read what GitHub already makes public. No scraping private content, no surprise OAuth scopes. Private repos are explicitly opt-in via the GitHub App.

No filler, no fluff

Every output has a rubric behind it. If a section doesn't have enough signal, we say so — instead of padding with generic 'consider adding analytics' advice.

You own the output

Every generated document is yours to paste, edit, screenshot, publish or sell. We don't claim any rights to what you make with Git Pitcher.

FAQ

The questions we hear most.

How long does a single run take?

The first token usually lands quickly after repo context is ready. Repo Read is the fastest path; Audit and Build Pack typically take longer because they do deeper reasoning.

Does it work on private repos?

Yes, on Pro. Install the Git Pitcher GitHub App on the repos (or organisations) you want to scan, and they'll show up as selectable inputs. You can revoke the app at any time from GitHub's settings.

What languages / frameworks does it understand?

All of them, in the sense that we reason from README, manifests and file structure. For the big ecosystems — JS/TS, Python, Go, Rust, Ruby, Java, Swift — we read manifests specifically to ground the tech-stack section.

Can I edit the output?

Yes. On Pro you can refine individual sections, ask for a deeper cut, and export to clean Markdown. On Free you get the full document and can copy-paste freely.

Is there a rate limit?

Plans use monthly credits. Free gets a small allowance, while Pro and Team get larger credit pools for heavier generation, refine, and revision usage.

See the outputs

Each mode has its own page with a breakdown of the structure, the use cases, and the kind of teams it fits.

Browse all features →