findings-to-gh-pr-review
Findings To Gh Pr Review
Turn concrete findings into precise pending PR review comments. Verify each finding in code before posting, anchor it to an actual changed diff line, and avoid duplicating existing threads.
Workflow
-
Identify the target PR. If the user gives a PR number or URL, use it. Otherwise infer the PR from the current branch with
gh pr view. Capture the PR number, base branch, head branch, and head SHA. -
Treat every finding as a claim to verify. Read the changed spec or source file, the relevant production code, and the PR diff around the target line. Do not post findings from a review summary alone.
-
Check whether the issue is already covered. Fetch existing review threads with
gh api graphql. If an open or pending thread already covers the same issue, prefer a thread reply or skip posting rather than duplicating the comment.