# Post Pr Review

> Post the findings from a `/pr-review` as a draft (PENDING) review on a GitHub PR. The review stays invisible until you manually click "Submit review" on GitHub.

- Skill: `satejbidvai/post-pr-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add satejbidvai/post-pr-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/satejbidvai/post-pr-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: satejbidvai (https://skillmd.com/u/satejbidvai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/satejbidvai/post-pr-review

---


Post the findings from a `/pr-review` as a draft (PENDING) review on a GitHub PR. The review stays invisible until you manually click "Submit review" on GitHub.

**Prerequisites**: Run `/pr-review <PR URL>` first in this conversation.

**Input**: No arguments required. Everything is parsed from the `/pr-review` output in this conversation.

**Steps**

1. **Parse the metadata header** from the `/pr-review` output. Look for the HTML comment:

   ```
   <!-- pr:{owner}/{repo}/{pr_number} sha:{headSha} -->
   ```

   Extract `owner`, `repo`, `pr_number`, and `headSha`. If not found, tell the user to run `/pr-review` first.

2. **Collect findings** from the `/pr-review` output. For each finding, extract:
   - `file`: from the `## \`web/...\`` heading
   - `line`: from the `Line N:` prefix, or `null` if the finding used `[not-in-diff]`
   - `body`: the finding text

   Findings without a file heading (PR-wide comments) go into the review `body`.

3. **Validate lines against the diff** — read `/tmp/pr-review-diff.json` (already written by `/pr-review`). Build a set of valid `{path, line}` pairs from the diff hunks. For each finding:
   - Line is in the valid set → inline comment: `{ path, line, side: "RIGHT", body }`
   - Path exists in the PR but line is not in the diff (or was `[not-in-diff]`) → **goes into the review `body`** under the file path heading (GitHub's API does not support file-level comments on draft reviews)
   - No path → goes into the review `body`

4. **Build the review payload** at `/tmp/pr-review.json`:
   - `commit_id`: the `headSha`
   - `body`: body-level findings formatted as file path headings (`**\`path/to/file.ts\`**`) followed by the finding text. Empty (`""`) if no body-level findings.
   - `comments`: only inline comments from step 3 (never use `subject_type: "file"` — the API rejects it)
   - **Strip prefixes from each comment body before posting:** remove `Line N:` (the inline placement makes it redundant), remove `nit:` and `Question:` prefixes
   - **Do not add any prefix or attribution** to the review body or comments (no "[Comment made with Cursor]" or similar)
   - **Omit the `event` field entirely** — this creates a PENDING (draft) review. Using `"event": "COMMENT"` submits immediately and cannot be undone.

5. **Submit**:

   ```bash
   gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews -X POST --input /tmp/pr-review.json
   ```

6. **Report** how many inline comments were posted and how many findings were placed in the review body. Remind the user to go to GitHub and click "Submit review" to make it visible.