personal-review-request

Manages PR review request, result, and follow-up comments on GitHub with explicit write authorization.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kosako/agent-tools --skill personal-review-request-kosako
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personal-review-request
Source: https://github.com/kosako/agent-tools/tree/main/shared/skills/personal-review-request
Command: npx skills add https://github.com/kosako/agent-tools --skill personal-review-request-kosako

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents accidental or unauthorized GitHub writes during AI-assisted code review by gating every PR comment behind explicit user authorization, and it keeps cross-AI reviews independent by routing each PR to the agent that did not author it. ## Core Features & Use Cases - Three-mode write gate: Distinguishes write-authorized requests (slash command or explicit posting intent), draft mode (comment proposal only, no diff fetch or posting until confirmed), and read-only delegation. - Mutual review routing: Inspects Co-Authored-By trailers across all commits to pick the opposite AI as reviewer, failing closed to human judgment on mixed or unknown authorship. - Untrusted-input discipline: Treats PR titles, bodies, diffs, and comments from others as data only, validates PR numbers and repo slugs before shell use, and pins review targets by verified OID rather than branch names. - Use Case: You ask the agent to request a review on PR #42; it drafts the request comment for your confirmation, routes the review to Codex because Claude authored the commits, and posts the severity-classified result only after your explicit approval. ## Quick Start Ask the agent to run /personal-review-request with a PR number to post a review request and results on that GitHub pull request.

Frequently Asked Questions about personal-review-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request an AI code review on a GitHub pull request?▼

Run /personal-review-request with the PR number, optionally adding --reviewer codex|claude and --repo owner/repo. The skill posts a review request comment, routes the review to the AI that did not author the commits, and posts severity-classified results back to the PR.

How does cross-review routing decide between Claude and Codex reviewers?▼

Routing inspects only the Co-Authored-By trailers of every commit in the PR. If all commits have a single AI author, the opposite AI reviews; mixed authorship, missing trailers, or undeterminable authors fail closed and require human decision.

Does asking to review a PR automatically post comments to GitHub?▼

No. An ambiguous request like "review this PR" enters draft mode: the skill shows the proposed comment in conversation and waits for explicit confirmation before fetching diffs or posting. Only an explicit slash command or clear posting intent authorizes GitHub writes.

Can this skill approve, merge, or push fixes after a review?▼

No. Write authorization covers only review request and result comments; it never extends to merge, approve, fix, commit, or push. Fixes happen only through a separate explicit request in the normal implementation workflow.

Why does the skill pin review targets by OID instead of branch name?▼

Branch and ref names come from GitHub and can move after being read, so fetching by ref gives no guarantee the reviewed code matches the PR. The skill verifies base and head OIDs against the local checkout and builds diffs from those OIDs.

What happens when the local checkout does not match the PR head?▼

The review stops with BLOCKED, reporting only the expected and actual OIDs. The skill never runs checkout, fetch, reset, or stash to fix the state; it asks the caller or a human to prepare a clean worktree before retrying.