How to Use GitHub user pull requests in dots
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 dots
Copy an example into dots, or ask in your own words.
Every Monday, use GitHub user pull requests for tiangolo covering the previous calendar week. Report newly seen proposal URLs with their titles, repositories, and states.
Each morning, use GitHub user pull requests for antfu covering the previous seven days. Show newly seen open proposals in repositories whose names contain vite.
Every Friday, use GitHub user pull requests for yyx990803 covering the previous 30 days. Group newly seen proposals by repository and include their creation dates and links.
Each week, use GitHub user pull requests for sindresorhus covering the previous calendar month. Compare matching URLs with the previous report and list any changes in reported state.
On the first of each month, use GitHub user pull requests for tiangolo covering the previous month. Prepare a reading list from titles mentioning documentation or CLI changes, with repository names and links.
How to set up GitHub user pull requests in dots
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send dots 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 Spiral's MCP server
- Create an API key
In the console, open API keys and create a key for your dot. Copy it.
- Send your dot this message
Your dot reads Spiral's skill and asks for your API key.
set up https://spiral.ai/SKILL.md
- Give your dot the key
When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.
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: dots 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 dots 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 dots?
Receive a recurring digest of newly opened public proposals in open-source projects you follow. A scheduled agent can compare returned GitHub URLs with earlier results and revisit older creation windows for changes in reported state.
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 dots
Overview
GitHub user pull requests in other agents
Questions about GitHub user pull requests in dots
Can dots use GitHub user pull requests?
Yes. Add Spiral to dots as an MCP server, and dots can find and run GitHub user pull requests like any built-in tool.
How much does GitHub user pull requests cost in dots?
$0.0013 per run. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.
Do I need a ScrapeCreators account to use GitHub user pull requests in dots?
You need no ScrapeCreators account. dots uses one Spiral API key for every tool, and Spiral runs GitHub user pull requests on its own ScrapeCreators account.
How long does it take to set up GitHub user pull requests in dots?
About two minutes: create an API key, then send your dot this message, then give your dot the key.
Does dots wait while GitHub user pull requests runs?
GitHub user pull requests runs in the background. dots 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 dots
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into dots:
set up https://spiral.ai/SKILL.md


