菜单
Mechanical half of /review - posts a pre-written review body to GitHub and auto-resolves any threads that the current HEAD has already addressed. Called by /review after the analysis is complete; can also be run standalone to re-post or to clean up resolved threads on an existing PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Polish an open PR for review. Classify the diff by bucket (frontend / python / go) and run only the relevant checks — Biome+tsc+Playwright for frontend, black+pylint+pytest for python, build+test for go. Address open review comments, update CLAUDE.md docs if stale, rewrite the PR title and description, then watch CI until all checks pass (diagnosing and reporting any failures). Use when the user wants to close out a PR, verify it's ready for review, or run /pr.
Senior engineer review of the open PR (or a specified PR number) across four lenses - scientific accuracy, sensitive language, maintainability, and accessibility. Delivers findings inline in the conversation as plain readable prose. Silently writes a GitHub-formatted version to /tmp/het-review.md for optional posting via /review-post. Advances health equity by catching data errors, harmful language, and a11y failures before they reach users.
Cut a new production release — pre-flight checks, auto-increment tag, publish GitHub release, monitor prod deploy, verify prod loads, targeted Playwright smoke tests, then trigger nightly E2E. Use when the user wants to ship a release or run /release.
Force-push the current branch to infra-test to trigger a GCP deploy, wait for it to complete, then run each associated DAG pipeline one at a time and wait for each to finish. On full success, updates the PR description with a checklist confirming real GCP infra-test results. Use when the user wants to verify backend changes on the test environment before merging, or run /infra-test.
Take responsive screenshots of the current branch's frontend work and embed them into the open PR's Screenshots section. Use when the user wants to capture UI screenshots for a pull request, add screenshots to a PR, or run /screenshot-pr.
Split a cluster of tangential file changes out of the current PR into a focused pre-PR (merges before) or follow-up PR (merges after). Both modes add merge-order notes to both PRs and cross-reference each other. Use when the user wants to extract unrelated changes from a feature branch, or run /split.
| name | review-post |
| model | haiku |
| description | Mechanical half of /review - posts a pre-written review body to GitHub and auto-resolves any threads that the current HEAD has already addressed. Called by /review after the analysis is complete; can also be run standalone to re-post or to clean up resolved threads on an existing PR. |
Post a pre-written review to GitHub and resolve threads that are already addressed. This skill handles only the mechanical steps; the analysis lives in /review.
Expects /tmp/het-review.md to exist with the review body and a first line matching:
VERDICT: request-changes|comment
If that file does not exist, print an error and stop.
The user may pass a PR number as an argument (e.g. /review-post 4764). If none is given, detect the open PR from the current branch.
head -1 /tmp/het-review.md # read VERDICT line
gh pr view --json number,headRefName
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
Strip the VERDICT: prefix line from the body before posting (it is metadata, not review content):
tail -n +2 /tmp/het-review.md > /tmp/het-review-body.md
gh pr review <number> --<request-changes|comment> --body-file /tmp/het-review-body.md
Print the URL of the posted review.
Fetch all open review threads:
gh api graphql -f query='{ repository(owner: "<owner>", name: "<repo>") { pullRequest(number: <n>) { reviewThreads(first: 50) { nodes { id isResolved body comments(first: 1) { nodes { databaseId body } } } } } } }'
For each unresolved thread, check whether the exact code or concern it references still exists in the current HEAD using git grep or git diff origin/main...HEAD. If the flagged code is gone or changed to address the concern, resolve the thread:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "<PRRT_id>"}) { thread { isResolved } } }'
Leave threads open where the concern is still valid or the resolution is ambiguous.
/review.