菜单
Investigate and resolve GitHub pull request review comments for HMIS. Use when the user wants Codex to read PR review threads, assess CodeRabbit or Codex feedback, discuss valid fixes, batch and apply changes, reply to each comment, and re-request review.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hmislk/hmis --skill review-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Run a live bug-demonstration capture session before filing GitHub issues. The user drives the browser and narrates bugs one after another ("see this — clicking X should do Y but does Z"); this skill captures each demo (snapshot + screenshot + description + environment context) without investigating, only after the user signals the session is over does it investigate root causes, then only after the user reviews the write-ups does it file issues. Use when asked to "demonstrate some bugs", "show you issues before filing them", or via `/demonstrate-issues`. Never fixes anything — it ends at filing GitHub issue(s); any actual fix is separate, later `dev-issue` work.
Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and the database, iterate until passing, record any testing-workflow learnings, commit/push, open a PR, and loop on review comments until mergeable. Use when asked to "take issue #N end to end", "do issue #N fully", "develop and ship issue #N", or similar full-cycle requests.
Run one or more GitHub issues through their full lifecycle end-to-end with NO pauses for user input — investigate, decide the approach, gather test context, and run the CI/review loop entirely autonomously, documenting every judgment call for after-the-fact review instead of asking. Accepts a single issue, a batch of issue numbers/URLs, or an unfiled bug/request described in plain text. Use ONLY when the user has explicitly said they will be unreachable (away from the computer, asleep, offline) and wants the issue(s) shipped as mergeable PR(s) without them. Do not use this for normal work — use dev-issue instead, which asks for input at the same points this skill auto-resolves.
| name | review-pr |
| description | Investigate and resolve GitHub pull request review comments for HMIS. Use when the user wants Codex to read PR review threads, assess CodeRabbit or Codex feedback, discuss valid fixes, batch and apply changes, reply to each comment, and re-request review. |
Use this skill when working a PR review loop on HMIS: collect review comments, verify them against the codebase, discuss unclear items with the user, apply confirmed fixes, and close the loop on GitHub.
Fetch the branch and inspect the PR comments.
git fetch origingh pr checkout <pr-number-or-url>gh api repos/hmislk/hmis/pulls/<pr-number>/commentsGroup comments by file and behavior.
rg, Get-Content, or git show.Discuss before changing anything ambiguous.
Apply confirmed fixes in a tight batch.
findLongByJpql for count queries.Check the repository-specific hazards before pushing.
persistence.xml placeholders remain ${JDBC_DATASOURCE} and ${JDBC_AUDIT_DATASOURCE}.<!DOCTYPE html> and use h:outputText for static ERP labels.Push, reply, and re-request review — by the cardinal rules below.
<commit-sha>: <what was changed>"<specific reasoning>"coderabbitai/chat/<sha> branch.POST /pulls/{pr}/comments/{id}/replies. Never as new top-level comments.Order: discuss → fix → push → reply to existing threads → one re-review request.
| Want | Endpoint | Use? |
|---|---|---|
| Reply under existing reviewer comment | POST /pulls/{pr}/comments/{id}/replies | YES |
| New standalone inline comment | POST /pulls/{pr}/comments | NO — creates a fresh thread |
| Bundled review wrapper | POST /pulls/{pr}/reviews | NO |
| General PR comment | POST /issues/{n}/comments | Sparingly, only for actual PR-wide notes |
# List existing comments to find a parent ID
gh api "repos/hmislk/hmis/pulls/<PR>/comments" \
--jq '.[] | "\(.id) \(.user.login) \(.path):\(.line // .original_line)"'
# Post a threaded reply (the only legitimate reply form)
gh api -X POST "repos/hmislk/hmis/pulls/<PR>/comments/<COMMENT_ID>/replies" \
-f body="Fixed in <commit-sha>: <what was changed>."
developer_docs/git/pr-review-workflow.mdAGENTS.md