find-best-reviewerslisted

# Find Best Reviewers Discover who actually reviews code in a GitHub repository. Answers two questions: 1. "Who should review my PR?" (path-aware) 2. "Who are the top reviewers in this repo?" (repo-wide) ## When to Use - Before submitting a PR to an unfamiliar repo — find who to expect reviews from - During oss-repo-recon — identify key maintainers - When CODEOWNERS is missing or incomplete - When scoping a contribution — find who owns a subsystem ## Parameters - **repoFullName**: `owner/repo` (required) - **paths**: list of file paths to filter by (optional — omit for repo-wide ranking) - **topic**: topic keyword for global discovery mode (optional — omit for single-repo) ## Step 0: Check CODEOWNERS Before doing any analysis, check if the repo already answers the question: ```bash # Check both standard locations gh api repos/{owner}/{repo}/contents/CODEOWNERS --jq '.content' 2>/dev/null | base64 -d gh api repos/{owner}/{repo}/contents/.github/CODEOWNERS --jq '.content' 2>/dev/null | base64 -d ``` If CODEOWNERS exists and covers the target paths, report those owners. Still run the analysis below to supplement — CODEOWNERS can be stale or incomplete. ## Step 1: Fetch PR + Review Data via GraphQL Use a single GraphQL query to fetch merged PRs with nested reviews and file paths. This is ~100x more efficient than REST (1 call vs 200+). ```bash gh api graphql -f query=' query($owner: String!, $repo: String!, $cursor: String) { repository(owner: $owner, name: $repo) {