github_api_paginated_search
/github_api_paginated_search
Fetch data from GitHub's Search API using the GitHub CLI (gh) while correctly handling pagination and merging results. Use this when you need to retrieve more than 100 items or ensure full dataset coverage for a specific period.
- Author
- cxcscmu ↗
- Repository
- SkillLearnBench ↗
- Licence
- MIT
- Last repository change
- 02.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Fetch data from GitHub's Search API using the GitHub CLI (gh) while correctly handling pagination and merging results. Use this when you need to retrieve more than 100 items or ensure full dataset coverage for a specific period.
Original author description
Fetch data from GitHub's Search API using the GitHub CLI (gh) while correctly handling pagination and merging results. Use this when you need to retrieve more than 100 items or ensure full dataset coverage for a specific period.
How it works
SKILL.md has no level-two headings · 16 lines, 152 words
SKILL.md preview
--- name: github_api_paginated_search description: Fetch data from GitHub's Search API using the GitHub CLI (gh) while correctly handling pagination and merging results. Use this when you need to retrieve more than 100 items or ensure full dataset coverage for a specific period. --- To fetch all items from a GitHub search query across multiple pages: 1. Use the `gh api` command with the `--paginate` flag. 2. Target the `search/issues` endpoint (which covers both Issues and Pull Requests). 3. Append your query using the `-f q="..."` parameter. 4. Use `jq` with the `-s` (slurp) flag to combine the separate JSON objects returned for each page into a single array of items. Example for fetching all PRs created in a specific month: ```bash gh api --paginate "search/issues" -f q="repo:cli/cli is:pr created:2024-12-01..2024-12-31" | jq -s 'map(.items) | add' > prs.json ``` Key considerations: - **Pagination**: Without `-s 'map(.items) | add'`, `jq` will only process the first page's object or encounter errors when trying to treat multiple JSON objects as a single stream. - **Separate Queries**: Use distinct queries for "created" and "closed" events to ensure accuracy, as an item created in one month might be closed in another.
Versions
The database has no other skills named github_api_paginated_search.
Database snapshot: 13.11.2026 · package version 2b8edfac4fd9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100evo-gh-data-fetcher
Fetches pull request and issue data from a GitHub repository using the GitHub REST API via curl/subprocess. Handles JSON output parsing, pagination, date range filtering, and error handling. Use when you need to retrieve structured PR or issue data from GitHub for analysis. - 96create-test
Use when create or update tests to ensure full coverage for current changes - 100github-commit-recovery
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers. - 100github-commit-recovery
Recover deleted commits from GitHub using REST API, web interface, and git fetch. Use when you have commit SHAs and need to retrieve actual commit content, diffs, or patches. Includes techniques for accessing "deleted" commits that remain on GitHub servers. - 100github-gh-cli
Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output. - 95github-cli
MUST USE for GitHub-related operations, including a GitHub URL, repository or code search, Issues, pull requests, Actions, Releases, permissions, and API requests. Use the local GitHub CLI (`gh`).