workflow-pr-review

Automated GitHub pull request reviews fetch the PR into an isolated worktree, run a reviewer agent, and post deduplicated inline comments before submitting a final decision. This orchestration ensures consistent, non-duplicative feedback directly on the code.

Deduplication for GitHub PR review comments matches new findings against existing review threads using fuzzy matching constraints, specifically line proximity and Jaccard token overlap. If a similar critique exists, it avoids re-posting and adds a reaction instead.

Yes, you can enrich GitHub PR review context using ticket references. If the PR title, body, or recent commits contain a ticket key, Confluence URL, or #number, the review workflow automatically incorporates that external context.

To submit an approve or comment decision for a GitHub PR review, the workflow enforces a strict review-decision footer contract. The reviewer agent must output this footer, which dictates the final state submitted to GitHub.

When a GitHub PR review agent posts comments outside the diff, it safely handles out-of-diff results through informational deferral, particularly during API 422 responses. It anchors inline comments using repo-relative paths to manage scope.

Yes, an isolated worktree is required to run a remote GitHub PR review. The workflow fetches the PR into an ephemeral worktree to execute the reviewer agent safely without affecting the local repository state.