Review PR Skill

Review the current pull request and write the output to review.json.

Context

• The working directory is the PR branch checkout.
• The workflow provides an annotated diff in pr_diff.txt.
• The workflow provides the PR description in pr_description.txt.
• Focus on files and lines changed by this PR.
• Do not post comments or reviews to GitHub directly.

Review Scope

• Prioritize correctness, security, error handling, and meaningful performance issues.
• Include style or nit comments only when you can provide a concrete suggestion block.
• If a concern involves untouched code, mention it in the summary instead of an inline comment.
• Do not suggest adding test cases that only vary constructor inputs or struct fields when the existing test already covers the meaningful behavior. Only suggest new tests when they exercise a distinct code path or edge case.
• When a PR is clearly a V0 or initial implementation, frame robustness suggestions (timeouts, retries, lifecycle management) as optional future work rather than blocking concerns, unless they risk correctness, security, or data loss.