Skip to content
Skills Library
Programming · Review & audit

inline-pr-comments

/inline-pr-comments

Post a single consolidated PR review with summary and inline comments. Use this skill to deliver code review feedback as one unified review per run.

Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Post a single consolidated PR review with summary and inline comments. Use this skill to deliver code review feedback as one unified review per run.

Original author description

Post a single consolidated PR review with summary and inline comments. Use this skill to deliver code review feedback as one unified review per run.

How it works

  1. When to Use
  2. Instructions
Original SKILL.md headings · 116 lines, 666 words
SKILL.md preview
---
name: inline-pr-comments
description:
  Post a single consolidated PR review with summary and inline comments.
  Use this skill to deliver code review feedback as one unified review per run.
---

# Consolidated PR Review Skill

Use this skill to submit code review feedback as a **single consolidated GitHub review** containing both the summary body and all inline comments.

## When to Use

- After completing a code review (use with /code-review, /security-review, /tob-review)
- When you have specific line-by-line feedback to deliver

## Instructions

Submit one consolidated review per run using the GitHub API. **Do NOT post inline comments individually.** Each run produces a new review — nothing is overwritten.

### Step 1: Fetch Prior Review Context

Before reviewing, read existing reviews and comments on the PR for context:

```bash
# Fetch existing reviews (summaries)
gh api --paginate "repos/$GITHUB_REPOSITORY/pulls/$PR_NUMBER/reviews" --jq '.[] | {user: .user.login, state: .state, body: .body}'

# Fetch inline review comments
gh api --paginate "repos/$GITHUB_REPOSITORY/pulls/$PR_NUMBER/comments" --jq '.[] | {user: .user.login, path: .path, line: .line, body: .body}'

# Fetch general PR discussion comments
gh api --paginate "repos/$GITHUB_REPOSITORY/issues/$PR_NUMBER/comments" --jq '.[] | {user: .user.login, body: .body}'
```

Use this context to:

- **Skip issues already raised** — don't re-flag something a prior review already pointed out
- **Reference prior discussions** — e.g. "As noted in the previous review, ..."
- **Flag unresolved issues** — if a prior review raised something that still isn't fixed, note it briefly (e.g. "Still unresolved from prior review: ...")
- **Avoid contradictions** — don't suggest the opposite of what a human reviewer requested

**Re-fetch immediately before submitting.** Other reviewers may be reviewing concurrently. Critically, the GitHub API does **not** expose a reviewer's draft/pending comments until they submit — so you can post a review seconds before a concurrent reviewer submits theirs and never have seen their notes. Re-run the fetch right before Step 4, and state the HEAD commit your review is based on in the body (e.g. "Reviewed at `<sha>`") so readers know the snapshot.

### Step 2: Collect All Findings

Complete the full review. Collect:

- **Summary** — Overall assessment, architecture concerns, non-diff observations
- **Inline comments** — Specific issues on changed lines (path, line, body)

### Step 3: Build Review JSON

Write a JSON file to `/tmp/review.json`:

```json
{
  "body": "## Review Summary\n\nOverall assessment here.\n\n## Observations Outside This PR\n- `file:line`: description",
  "event": "COMMENT",
  "comments": [
    {
      "path": "src/file.ts",
      "line": 42,
      "body": "Issue description here"
    },
    {
      "path": "src/other.ts",
      "start_line": 10,
      "line": 15,
      "body": "Multi-line comment"
    }
  ]
}
```

**Fields:**

- `body` — Markdown review summary (required)
- `event` — Always `"COMMENT"` (never APPROVE or REQUEST_CHANGES)
- `comments` — Array of inline comment objects (can be empty if no inline findings)
  - `path` — File path relative to repo root
  - `line` — Line number in the NEW version of the file
  - `start_line` + `line` — For multi-line comments
  - `body` — Markdown-formatted feedback

### Step 4: Submit the Review

```bash
gh api "repos/$GITHUB_REPOSITORY/pulls/$PR_NUMBER/reviews" --input /tmp/review.json
```

The `GITHUB_REPOSITORY` and `PR_NUMBER` environment variables are set by the CI workflow.

### Limitations

- Inline comments can only target lines in the diff (changed/added lines)
- Comments targeting unchanged lines will cause the API call to fail
- If unsure whether a line is in the diff, put the finding in the summary body instead

### Handling Non-Diff Findings

Issues in code NOT changed by the PR go in the review `body` under a dedicated section:

```markdown
## Observations Outside This PR

- `src/utils/foo.ts:142`: Pre-existing null check missing
- `src/core/bar.ts:78-82`: Similar pattern to line 45 issue
```

### Feedback Guidelines

| Feedback Type                 | In Diff? | Where to Put It                                      |
| ----------------------------- | -------- | ---------------------------------------------------- |
| Specific code issue           | Yes      | `comments` array entry for that line                 |
| Pattern repeated across files | Yes      | First occurrence in `comments` + note others in body |
| Related issue found           | No       | `body` under "Observations Outside This PR"          |
| Pre-existing bug discovered   | No       | `body` (consider separate issue if critical)         |
| Overall architecture concern  | N/A      | `body`                                               |

Be concise. Group minor style issues together. Never use APPROVE or REQUEST_CHANGES.

Versions

RepositoryScoreLicence
This page · hyperlane-xyz/hyperlane-monorepo100Apache-2.0
hyperlane-xyz/hyperlane-warp-ui-template100Apache-2.0

Database snapshot: 13.11.2026 · package version e9a8a45c5c77 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pr-review-comments
    Guide for submitting/posting inline PR review comments to GitHub. Use this when you need to post code review comments on specific lines of a Pull Request.
  • 100skill-code-review
    Expert multi-AI code review with inline PR comments — use for thorough quality and security analysis
  • 100pr-review-comments
    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them…
  • 100review-pr
    Use when reviewing a pull request, posting PR review comments, or when user says /review-pr. Reviews code with parallel agents and posts a pending GitHub review with inline comments.
  • 100github-pr-workflow
    Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
  • 100pr-review-post
    Post a GitHub PR review (verdict + inline comments) in one API call. Use when posting, submitting, or publishing a "PR review", "code review", "review with inline comments", "approve the PR", "request changes", or any payload bound for `gh api repos/*/pulls/*/reviews`. Triggers…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.