pr-review-guide

Load this skill when posting review comments on a GitHub pull request.

Line Number Tracking

When analyzing a PR diff, Always record exact file paths and line numbers for every finding as you go. Each finding must include the precise path and line (and start_line for multi-line ranges) in the new file (right side of the diff) needed to post a review comment. Do not defer line number resolution to a later step.

When the review is performed by a sub-agent, the agent's returned findings must include these fields per finding so the caller can post comments immediately:

• path: file path relative to repo root
• line: line number in the new file (end line for multi-line)
• start_line (optional): start line for multi-line comments
• body: the comment text, ready to post

Posting Review Comments