Menú
Read GitHub issues and pull requests via the REST API instead of scraping HTML pages.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Set up a git worktree to run and evaluate an upstream Pull Request locally in a flat worktree bare clone repository layout.
Sync a fork's main branch with upstream and rebase local feature branches. Designed for the triangle workflow where development happens in fork feature branches and PRs go to the upstream repo.
Basado en la clasificación ocupacional SOC
| name | read-github |
| description | Read GitHub issues and pull requests via the REST API instead of scraping HTML pages. |
When a user references a GitHub issue or PR URL (e.g.
https://github.com/PAIR-code/deliberate-lab/issues/NNN or
.../pull/NNN), use the GitHub REST API to fetch clean JSON rather
than fetching the HTML page. The HTML is dominated by navigation chrome,
CSS, and JavaScript — making it difficult to extract the actual content.
API endpoints follow the standard pattern:
https://api.github.com/repos/{owner}/{repo}/issues/{number}https://api.github.com/repos/{owner}/{repo}/pulls/{number}The issue/PR endpoint does not include comments inline — they are
only available via a separate request. Check the comments field in the
response. If it is greater than zero, fetch them:
https://api.github.com/repos/{owner}/{repo}/issues/{number}/commentsIssue and PR comments often contain supplementary guidance, research findings, design decisions, and other context critical to understanding the work. Do not skip them.