review-a-pr
Have a Rush cloud agent review a GitHub pull request and report what it would change. Use when someone asks for a code review, a second opinion on a PR, or a check of a PR before merging.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- review-a-pr
- description
- Have a Rush cloud agent review a GitHub pull request and report what it would change. Use when someone asks for a code review, a second opinion on a PR, or a check of a PR before merging.
03 SKILL.md 正文
Review a pull request with Rush
- Find the pull request. Get its URL. If the person names only a
repository, ask which PR. If
list_repositoriesdoes not list the repository, say the Rush GitHub App does not reach it yet (https://cloud.getrush.ai/console/settings/?section=connections) and stop. - Start the review. Call
create_sessionwith the PR URL asrepo, a fresh UUID you write yourself asrequest_id, and atasklike: "Review this pull request. Read the diff and the code it touches, run the tests and linters the repo has, and list each problem with its file and line, why it matters and the change you would make, most serious first. Say plainly if you find nothing. Do not push commits or post comments." Add anything the person asked to focus on, such as security or performance. To review several PRs, start one session each. - Wait. A review takes a few minutes: call
wait_for_sessionswithtimeout_seconds: 50until it settles. - Report. From
get_session: the findings, most serious first, each with its file and line, and which tests ran. Do not add findings of your own to Rush's list. Onneeds_revieworfailed, say so with the reason. - Offer the next step. Ask follow-up questions with
send_session_messagein the same session; its task told it not to push. To make the fixes, start a new session with the findings in itstaskand the PR's branch (/tree/<branch>) asrepofor a branch in the same repository; for a PR from a fork, the new session opens its own pull request. Start it only when the person asks.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.