From Dev10x
Request review on a GitHub PR from teams or users. TRIGGER when: PR is ready for review and needs reviewer assignment. DO NOT TRIGGER when: PR is still draft or WIP, or review was already requested.
npx claudepluginhub dev10x-guru/dev10x-claude --plugin Dev10xThis skill is limited to using the following tools:
This skill follows `references/task-orchestration.md` patterns.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
This skill follows references/task-orchestration.md patterns.
Create a task at invocation, mark completed when done:
REQUIRED: Create a task at invocation. Execute at startup:
TaskCreate(subject="Request PR review", activeForm="Requesting review")Mark completed when done: TaskUpdate(taskId, status="completed")
Request reviews on GitHub pull requests from teams or individual users. Auto-resolves reviewers from per-project config when available.
The skill resolves reviewers in this order:
~/.claude/memory/Dev10x/github-reviewers-config.yaml
and look up the current repo's project entrydefault_action: askThe config file is optional. If it does not exist or lacks an entry
for the current repo, the skill falls back to default_action
behavior (ask or skip).
# ~/.claude/memory/Dev10x/github-reviewers-config.yaml
default_action: ask # "skip" or "ask" for unconfigured projects
projects:
app-pos:
reviewers:
- example-org/backend-devs
Dev10x-ai:
skip: true
owner/repo)reviewers list uses GitHub format: org/team-slug for teams,
username for individual usersskip: true suppresses the review request for that projectdefault_action: ask prompts the user for unconfigured projects;
skip silently skips themBefore requesting review, verify the PR is not in draft state. GitHub silently accepts review requests on draft PRs but does NOT notify the requested reviewers — the request is lost.
mcp__plugin_Dev10x_cli__pr_detect
or gh pr view --json isDraft --jq .isDraftisDraft == true: run gh pr ready first, then proceedisDraft == false: proceed to reviewer resolutiongh repo view --json name --jq .nameyq:
yq '.projects["REPO_NAME"]' ~/.claude/memory/Dev10x/github-reviewers-config.yamlprojects:
skip: true → print "Skipping review request
for {repo}" and stopreviewers list → use those reviewersdefault_action: ask → REQUIRED: Call
AskUserQuestion to ask the user who to request review
from (do NOT use plain text)default_action: skip → print "No reviewers
configured for {repo}, skipping" and stoprequest_review MCP tool with the resolved reviewersInvoke the skill without arguments. It reads the config, detects the current repo, and requests review from the configured reviewers:
/Dev10x:gh-pr-request-review
Pass reviewer names directly to skip config lookup:
mcp__plugin_Dev10x_cli__request_review(
pr_number=PR_NUMBER, reviewers=["org-name/team-slug"], team=true)
mcp__plugin_Dev10x_cli__request_review(
pr_number=PR_NUMBER, reviewers=["user1", "user2"])
gh pr view PR_NUMBER --json reviewRequests \
--jq '.reviewRequests[].login // .reviewRequests[].name'
request_review MCP tool for requesting reviews (handles
both users and teams)org-name/team-slugreviewRequestsIf team review request returns HTTP 422 (e.g., team not found, team has no access to the repo, or org settings prevent team reviews), fall back to requesting from individual team members:
gh api orgs/{org}/teams/{slug}/members --jq '.[].login'This pattern was discovered in audit session GH-446 where the team request consistently returned 422.