菜单
Resolve a GitHub pull request (from a link, number, or the current branch) and fetch its details, diff, and review threads. Use when: looking up a PR, pulling PR context, fetching a pull request and its comments. Building block for other skills that operate on a PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.
| name | read-pr |
| description | Resolve a GitHub pull request (from a link, number, or the current branch) and fetch its details, diff, and review threads. Use when: looking up a PR, pulling PR context, fetching a pull request and its comments. Building block for other skills that operate on a PR. |
| argument-hint | Optional: PR link, org/repo#123, or bare number — defaults to the current branch |
Resolve a pull request and fetch everything a caller needs to reason about it. This is a read-only building block — fetch and read, never post or modify. Other skills call it to get PR context.
Determine the repo and PR number:
https://github.com/org/repo/pull/123) → parse org/repo and 123org/repo#123) → same123) → use the current repo's origin remoteIf no PR can be resolved, report that clearly (and ask for a link/number) rather than guessing.
Use the GitHub MCP tools to retrieve:
Hand back a structured summary the caller can use directly:
**<org/repo>#<number>: <title>** (<state>) — @<author>
base `<base>` ← head `<head>`
<one-line description from the PR body>
**Changed files:** <count> (<rough sense of scope>)
**Review threads:** <N unresolved, M resolved> (or "none")
Keep the diff and thread details available for the caller — this skill gathers and structures; it does not review, fix, or post anything.