Stats
Actions
Tags
From swe
Use when user asks who reviews code, finds a reviewer, needs a code review contact, or asks who should review their merge request. This is specifically for CODE REVIEW only - use worker:find-poc for all other POC requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/swe:find-code-reviewerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find the appropriate person to contact for code review based on team structure, code ownership, and project context.
Find the appropriate person to contact for code review based on team structure, code ownership, and project context.
NOT for non-code POC - use worker:find-poc instead.
REQUIRED SUB-SKILL: Use worker:search-memory to find team and code review information.
Search for:
Look for CODEOWNERS file in the repository:
find . -name "CODEOWNERS" -type f
Common locations:
.github/CODEOWNERSdocs/CODEOWNERSCODEOWNERS (root)Read the file to identify who owns which paths.
For files the user modified, find recent contributors:
git blame <file> | head -20
Identify who made recent changes - they may be good reviewers.
Check recent merge requests to see who typically reviews:
git log --oneline -20
Or check the Git hosting platform for recent reviewers.
Based on findings, determine:
Format the results:
# Code Reviewer
**Name:** [Name]
**Role:** [Role]
**Best Contact:** [Slack/Teams/Email]
**Why:** [Why they're the right reviewer]
If no clear reviewer found:
npx claudepluginhub peiyuanqi/work-like-me --plugin sweRoutes work to the right people using CodeScene ownership data. Connects files or directories to likely reviewers and domain experts.
Recommends RFC reviewers by analyzing file paths, prior commenters, and team mappings. Shows a ranked list with rationale, then requests reviewers on approval.