Pr Reviewer

instructions

1. Identify Target: Determine the target PR number and repository. If the user does not provide a PR number, execute gh pr status to find the PR associated with the current branch.
2. Extract Repository Context: Execute gh repo view --json owner,name -q '{owner: .owner.login, repo: .name}' to determine the {owner} and {repo} names.
3. Fetch Diff: Retrieve the patch diff for the target PR by executing gh pr diff <number> --patch.
4. Analyze Code: Perform a standard code review on the diff, focusing on architectural improvements, potential bugs, edge cases, readability, and best practices. Do not focus exclusively on security unless specifically asked.
5. Format Payload: Construct the review feedback into a specific JSON structure required by the GitHub API. The event MUST default to COMMENT.

   {
     "body": "General review summary message here.",
     "event": "COMMENT",
     "comments": [
       {
         "path": "path/to/modified/file.ext",
         "line": 123,
         "body": "**Suggestion:** Detailed feedback..."
       }
     ]
   }