post-pr-comments

Post inline code review comments on the GitHub PR associated with the current branch.

Step 1: Gather Findings

Collect all code review findings, issues, or suggestions from the current conversation. For each finding, determine:

• File path — relative to the repo root
• Line number(s) — the specific line or line range in the current version of the file
• Comment body — a clear, actionable description of the issue in markdown

If there are no review findings in the conversation, tell the user and stop.

Step 2: Resolve Line Numbers

For each finding, verify the line numbers are accurate:

1. Read the file to confirm the code at the referenced line matches what was discussed
2. If the line has shifted (e.g., due to edits since the review), find the correct current line
3. For issues spanning multiple lines, use start_line and line to define the range

Step 3: Write Comments JSON

Write a JSON file containing the comments array:

COMMENTS_FILE=$(mktemp /tmp/pr-review-comments-XXXXXX.json)

Each comment object must have:

• path (string) — file path relative to repo root
• line (number) — the line number (or end line for ranges)
• side (string) — always "RIGHT"
• body (string) — markdown comment body

For multi-line ranges, also include:

• start_line (number) — first line of the range
• start_side (string) — always "RIGHT"

Required footer

Append an attribution footer to the end of every comment body, so reviewers know the finding was machine-generated and at what rigor. Format:

\n\n---\n<sub>🤖 Analysis: <MODEL> · <REASONING> reasoning effort<EXTRA></sub>

• <MODEL> — the model that produced the analysis, e.g. Claude Opus 4.8.
• <REASONING> — the reasoning/thinking level used, e.g. high.
• <EXTRA> — optional · <note> suffix for extra provenance that genuinely applies, e.g. · red-teamed before posting when findings were adversarially verified. Omit entirely if nothing extra applies — do not fabricate it.