The prompt behind any repo or site.

Paste a public GitHub repository or a website address. Get the request that could have built it, short or as a full spec.

vercel/next.jsIllustrative example

Swap the domain, skip the form.

Replace github.com with gitprompt.dev in any repo link. Links to folders, issues and pull requests work too. For a website, put its address after gitprompt.dev/site/.

github.com/vercel/next.js

gitprompt.dev/vercel/next.js

Try it on a real repo.

facebook/reactTry It
vercel/next.jsTry It
pallets/flaskTry It
denoland/denoTry It

How it works

01
Paste a repo or site
Enter owner/repo, any github.com link, or a website address. Folders, issues and pull requests work too.
02
We read it
For a repo: the description, language, root files and README. For a site: the page's title, description and visible text. The stack is detected from manifests or page markers, not guessed by the model.
03
Copy the prompt
Take the short version or the structured spec, and paste it into your AI coding assistant.

One click from any repo.

Drag this to your bookmarks bar, then click it on any GitHub repository page to open it here.

Open in gitprompt

In your terminal.

The prompt goes to stdout, so it pipes anywhere.

npx gitprompt-cli vercel/next.js

Or in your agent.

Add the MCP server and your agent can ask for any repo's prompt itself.

claude mcp add gitprompt -- npx -y gitprompt-cli --mcp

What it is not

A plausible prompt, not the author's real one.
A request to build the project, not a summary or docs.
The website reads public repositories and websites. Private repos work from the command line. A site is read one page at a time, and pages that need JavaScript to render can come out thin.
No account, no install, no tracking.