Agent skill

Review PR

by hmislk in hmislk/hmis

Investigate and resolve GitHub pull request review comments for HMIS.

GPL-3.0Auto-check passedDevelopment

Install Review PR

skills CLI
$ npx skills add hmislk/hmis --skill review-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hmislk/hmis review-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/review-pr .claude/skills/review-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-pr
GitHub stars
236
Token cost
~1.1k tokens
SKILL.md length
472 words
Files
2
Skills in repo
33
Repo updated
First seen
Licence
GPL-3.0

At a glance

Investigate and resolve GitHub pull request review comments for HMIS.

  • Works in 6 steps: Fetch the branch and inspect the PR… → Group comments by file and behavior. → Discuss before changing anything… → …
  • The user wants Codex to read PR review threads
  • SKILL.md covers Overview, Workflow, Cardinal Rules for Posting on… and Endpoint Cheat Sheet, plus 2 more sections
  • Calls gh and git

What it does

Review PR is an agent skill from hmislk/hmis. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: This is an Open Source Java EE based Hospital Information Management System. The licence is GPL-3.0.

When your agent uses it

  • The user wants Codex to read PR review threads
  • Assess CodeRabbit
  • Discuss valid fixes
  • Batch and apply changes

Example prompts

  • “/review-pr”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Fetch the branch and inspect the PR comments.
  2. Group comments by file and behavior.
  3. Discuss before changing anything ambiguous.
  4. Apply confirmed fixes in a tight batch.
  5. Check the repository-specific hazards before pushing.
  6. Push, reply, and re-request review — by the cardinal rules below.

What it can do on your machine

Read from SKILL.md and the folder at commit d261e32. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review PR loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hmislk/hmis at commit d261e32, republished under its GPL-3.0 licence (© hmislk). 472 words, ~1,061 tokens.

Download SKILL.mdSave it as .claude/skills/review-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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.

Review PR

Overview

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.

Workflow

  1. Fetch the branch and inspect the PR comments.

    • git fetch origin
    • gh pr checkout <pr-number-or-url>
    • gh api repos/hmislk/hmis/pulls/<pr-number>/comments
  2. Group comments by file and behavior.

    • Read the touched code and nearby context with rg, Get-Content, or git show.
    • Separate valid findings from false positives and project conventions.
  3. Discuss before changing anything ambiguous.

    • Ask the user when a reviewer suggestion could change behavior, contracts, or workflow.
    • Prefer confirmation over guessing when automated review output is uncertain.
  4. Apply confirmed fixes in a tight batch.

    • Keep unrelated cleanup out of the review-fix commit.
    • Preserve HMIS rules: no constructor signature edits, no mock data, JPQL first, findLongByJpql for count queries.
  5. Check the repository-specific hazards before pushing.

    • Verify persistence.xml placeholders remain ${JDBC_DATASOURCE} and ${JDBC_AUDIT_DATASOURCE}.
    • For JSF/XHTML fixes, keep standard <!DOCTYPE html> and use h:outputText for static ERP labels.
  6. Push, reply, and re-request review — by the cardinal rules below.

Cardinal Rules for Posting on a PR

  1. Do NOT create new top-level inline comments on the PR. Each one becomes a thread the author must manually resolve. Self-review noise is the most common offender.
  2. Reply only after fixing (or explicitly dismissing). Bots cannot fix anything — describe action taken, not requested.
    • Valid + fixed → "Fixed in <commit-sha>: <what was changed>"
    • Dismissed → "Dismissed because: <specific reasoning>"
    • ⚠️ "Please resolve" wording on a CodeRabbit thread triggers CodeRabbit Chat, which opens a NEW PR attempting the fix against a stale snapshot. These auto-PRs have shipped unsafe diffs in the past (PR #20979). If accidentally triggered: close the PR, delete the coderabbitai/chat/<sha> branch.
  3. Replies go UNDER existing reviewer threads only — use POST /pulls/{pr}/comments/{id}/replies. Never as new top-level comments.
  4. Self-review items go in the commit message (or PR description if deferred). Never as new inline comments. Reference file:line in the commit message so reviewers can find the change in the diff.
  5. ONE re-review request at the end — click "Re-request review" once after all fixes are pushed and all existing threads have replies. Not per item.
Show full SKILL.md (104 more words)Show less

Order: discuss → fix → push → reply to existing threads → one re-review request.

Endpoint Cheat Sheet

WantEndpointUse?
Reply under existing reviewer commentPOST /pulls/{pr}/comments/{id}/repliesYES
New standalone inline commentPOST /pulls/{pr}/commentsNO — creates a fresh thread
Bundled review wrapperPOST /pulls/{pr}/reviewsNO
General PR commentPOST /issues/{n}/commentsSparingly, only for actual PR-wide notes
bash
# 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>."

Common Review Patterns

  • CodeRabbit suggestions often need verification against the actual entity or controller method names.
  • Review comments about null checks, constructor changes, or typos may be false positives in this codebase.
  • When a reviewer points to session-scoped state, re-check the persisted entity at submit time before mutation.

Reference

  • developer_docs/git/pr-review-workflow.md
  • AGENTS.md

© hmislk, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/review-pr of hmislk/hmis.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit d261e32

Compare with similar skills

Review PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review PR this skillhmislk/hmis236—~1.1kAutomated safety check: PassGPL-3.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from hmislk/hmis

All 33 skills in this repo
  • API Usage

    hmislk/hmis

    Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis.

    236 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Application configuration options reference for the HMIS project.

    236 GitHub stars~474 tokensUpdated today
    Auto-check passed
  • Caveman

    hmislk/hmis

    Ultra-compressed communication mode. An agent skill from hmislk/hmis.

    236 GitHub starsUsed in 20 repos~946 tokens
    Auto-check passed
  • Database Guide

    hmislk/hmis

    MySQL database development guide for the HMIS project. An agent skill from hmislk/hmis.

    236 GitHub stars~664 tokensUpdated today
    Auto-check passed
  • Demo Video

    hmislk/hmis

    A skill your agent uses when asked to make a demo, training, how-to or tutorial video with sound or voice-over showing an HMIS function or configuration (e.g.

    236 GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Deploy QA

    hmislk/hmis

    Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.

    236 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Review PR

What does Review PR do?

Investigate and resolve GitHub pull request review comments for HMIS. Review PR is an agent skill from hmislk/hmis. Investigate and resolve GitHub pull request review comments for HMIS.

When should I use Review PR?

Review PR fits situations like: the user wants Codex to read PR review threads; assess CodeRabbit; discuss valid fixes; batch and apply changes.

How do I install Review PR in Claude Code?

Run `npx skills add hmislk/hmis --skill review-pr -a claude-code`. Or copy the skill folder (.codex/skills/review-pr in hmislk/hmis) into .claude/skills/review-pr in your project. Claude Code loads it when a task matches its description.

How do I install Review PR in Codex?

Run `npx skills add hmislk/hmis --skill review-pr -a codex`. Or copy the skill folder (.codex/skills/review-pr in hmislk/hmis) into .agents/skills/review-pr in your project. Codex loads it when a task matches its description.

Can I use Review PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hmislk/hmis --skill review-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-pr, .gemini/skills/review-pr, .github/skills/review-pr and .opencode/skills/review-pr in your project.

What does Review PR need to run?

Going by SKILL.md and its folder, Review PR needs the command-line tools its instructions call (gh and git).

Does Review PR access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review PR use?

Review PR is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review PR use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review PR?

Skills that share tags, products or a category with Review PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review PR?

hmislk (a GitHub organization) maintains it in hmislk/hmis, which has 236 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.

Source: hmislk/hmis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.