// 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.
| 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.mdHandle CodeRabbit and Codex review comments on a GitHub PR. Fetches the PR, investigates each comment against the codebase, discusses validity with the user, batches valid fixes, and guides through push and reply steps.
JSF AJAX update rules for the HMIS project. Use when working on AJAX updates, p:commandButton update attributes, PrimeFaces AJAX callbacks, partial page rendering, or debugging AJAX update failures. Also covers JSF navigation patterns: why f:viewAction must not be used on @SessionScoped beans, and how initialization belongs in navigation methods. Critical rules to prevent silent AJAX failures and refresh/back-button state corruption.
JSF AJAX update rules for the HMIS project. Use when working on AJAX updates, p:commandButton update attributes, PrimeFaces AJAX callbacks, partial page rendering, or debugging AJAX update failures. Also covers JSF navigation patterns: why f:viewAction must not be used on @SessionScoped beans, and how initialization belongs in navigation methods. Critical rules to prevent silent AJAX failures and refresh/back-button state corruption.
Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.
Full environment setup when starting work on a GitHub issue. Creates a feature branch from origin/development, swaps persistence.xml to local JNDI settings, assigns the issue, and guides project board setup. Use when beginning work on any new issue: "start issue 20408", "/start-issue 20408", or "prepare env for issue 20408".
Verify and manage persistence.xml configuration around git push. Use before pushing to ensure environment variable placeholders are in place, and after pushing to restore local JNDI names for continued testing. Prevents QA deployment failures from hardcoded datasource names.