# Post Inline Review > Use when posting inline review comments, the per-agent summary review, or interacting with GitHub review threads (resolve, un-resolve, reply) for an F Prime PR review agent. - Skill: `nasa/post-inline-review` (Agent Skill) - Install (CLI): `npx skillmds@latest add nasa/post-inline-review` - Raw SKILL.md: https://api.skillmd.com/api/skills/nasa/post-inline-review/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: nasa (https://skillmd.com/u/nasa) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/nasa/post-inline-review --- # Skill: Post an inline review on a GitHub PR Reusable procedure for any F Prime review agent that needs to post inline review comments, the per-agent summary review, or interact with GitHub review threads (resolve / un-resolve / reply). This skill assumes: - An appropriately-permissioned token is exposed as `${TOKEN}` in the environment (provided by whatever external trigger invoked the agent). Required scopes: read access to the repository, write access to pull-request reviews, and write access to discussions / review threads for the GraphQL mutations. - The agent knows the owner, repo, PR number, head commit SHA, and its own short name (matches the `agent-registry.yml` entry). --- ## 1. Suggestion-block syntax GitHub renders a fenced block whose info string is exactly `suggestion` as a one-click "Apply suggestion" diff against the line range the comment is anchored to. ```markdown [Security] **must fix** Unbounded copy from ground argument. Validate `len` against the destination buffer before copying. The incoming `len` is ground-controlled and can exceed `sizeof(dst)`. ```suggestion if (len > sizeof(dst)) { return Status::INVALID_LENGTH; } memcpy(dst, src, len); ``` ``` The suggestion block replaces the entire line range the comment is anchored to. For multi-line replacements, anchor the comment to the full range (`start_line` + `line`) rather than a single line. --- ## 2. Posting one review with many inline comments A single PR review can carry many inline comments. Prefer one review per agent run rather than many small reviews — the GitHub UI groups them together. **First run** — the metadata block (see §4) goes in `body` alongside the inline `comments[]`: ```http POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews Authorization: Bearer ${TOKEN} Accept: application/vnd.github+json Content-Type: application/json { "commit_id": "", "event": "COMMENT", "body": "