How to Use GitHub user pull requests in Amp
Get public pull requests authored by a GitHub account, with titles, repositories, states, creation times, and links. Use it to find proposed changes across repositories or build a dated change digest.
Prompts to try with GitHub user pull requests in Amp
Copy an example into Amp, or ask in your own words.
Use GitHub user pull requests for tiangolo for October 2026. Compare the returned repositories with this project's dependency files and write a Markdown table of relevant titles, states, creation dates, and links.
Use GitHub user pull requests for antfu from September through October 2026. Match repository names against package.json and create a review queue of proposals affecting our dependencies.
Use GitHub user pull requests for yyx990803 for October 2026. Search returned titles for terms found in our Vue migration notes and save the matching proposal links beside those terms.
Use GitHub user pull requests for sindresorhus for October 2026. Create a CSV of the returned title, repository, state, creation time, and URL, grouped by repository.
Use GitHub user pull requests for tiangolo from July through September 2026. Draft a docs review checklist from titles mentioning CLI or configuration changes, linking each item to its proposal.
How to set up GitHub user pull requests in Amp
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
No header and no client ID or secret: Amp registers itself with Spiral.
amp mcp add spiral https://api.spiral.ai/mcp
- Sign in
Start amp. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.
- Check it
amp mcp doctor
Use the Spiral skill
- Send Amp this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run GitHub user pull requests
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "scrapecreators", "model": "scrapecreators/github-user-pull-requests", "input": { "handle": "torvalds" } }'
Then paste one of the prompts above: Amp finds GitHub user pull requests on Spiral, shows the price and runs it.
GitHub user pull requests providers and prices
Spiral runs GitHub user pull requests through ScrapeCreators. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Amp for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Cursor | a number | Cursor from the previous response. Defaults to 1. |
Every API field of GitHub · Pull Requests is on its tool page: open its card above.
What can you do with GitHub user pull requests in Amp?
Build an upstream proposal report for the repositories your project depends on. A coding agent can match returned GitHub pull request titles and repository names against project files, then save a linked review queue.
Draft a proposed-change digest
Turn an open-source creator's public pull request titles into a dated digest, grouped by repository and linked to the original proposals.
Find upstream fixes to investigate
Search returned titles for a dependency or bug mentioned in your project, then build a shortlist of pull request links for technical review.
Prepare a documentation review queue
Identify titles suggesting renamed options, new commands, or deprecated behavior. Give documentation editors the repository, creation date, and proposal link.
Review open proposals in a dependency
Keep returned open pull requests for repositories your product depends on, with titles and links for maintainers to inspect.
Build a proposal chronology
Arrange retrieved pull requests by creation time to document when public changes were proposed. Keep closed proposals separate from claims about released features.
Organize changes across repositories
Group an open-source creator's returned pull requests by destination repository so a project update can cover proposals spread across several codebases.
More on GitHub user pull requests and Amp
Overview
GitHub user pull requests in other agents
Questions about GitHub user pull requests in Amp
Can Amp use GitHub user pull requests?
Yes. Add Spiral to Amp as an MCP server, and Amp can find and run GitHub user pull requests like any built-in tool.
How much does GitHub user pull requests cost in Amp?
$0.0013 per run. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.
Do I need a ScrapeCreators account to use GitHub user pull requests in Amp?
No. Spiral runs GitHub user pull requests on its own ScrapeCreators account. You sign in to Spiral once and never paste a key.
How long does it take to set up GitHub user pull requests in Amp?
About two minutes: add the server, then sign in, then check it.
Does Amp wait while GitHub user pull requests runs?
GitHub user pull requests runs in the background. Amp starts the run, checks on it and gives you the json when it's ready.
Does this include private pull requests?
No. The endpoint documents public pull requests authored by the requested GitHub account; private repository activity is outside its stated coverage.
What information comes back for each pull request?
The documented response contains five pull request fields: title, repository, state, creation timestamp, and GitHub URL.
Does a closed pull request mean the change shipped?
No. GitHub allows pull requests to be closed without merging, so a closed state alone does not establish that the proposed code was incorporated.
Is the returned data guaranteed to be accurate?
ScrapeCreators explicitly does not guarantee data accuracy or availability. Its documented response provides a GitHub URL for checking the original pull request.
Can public GitHub data be used for unsolicited outreach?
GitHub prohibits using collected information for unsolicited emails or selling personal information to recruiters, headhunters, and job boards. Public visibility does not remove those restrictions.
Start using GitHub user pull requests in Amp
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Amp:
set up https://spiral.ai/SKILL.md


