メニュー
Read a pull request diff like a senior engineer. Flag risk, suggest tests, point out missing edge cases. Use when the user asks to "review PR", "look at this diff", or pastes a GitHub PR URL.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Strip the AI-isms out of any text — em-dash overuse, "It's not just X, it's Y", inflated significance, sycophantic openers, rule-of-three padding. Use when the user says "humanize this", "make this less AI", "tighten this", or pastes obviously-AI prose and asks for a rewrite.
Answer a natural-language question by writing a SELECT against the user's connected database via the QueryBear MCP. Use when the user asks "how many", "which users", "what's our", "give me a list of", or otherwise asks a question whose answer lives in their database.
Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved. Use when the user says "grill me", "stress-test this plan", "poke holes in this", or "what am I missing".
Look at what the user keeps re-explaining to the agent and propose new SKILL.md files that would replace those repeated explanations. Use when the user says "what skills should I have", "suggest skills", "audit my skills", or when you notice you're being asked the same kind of task three times in a row.
Take a raw bug report and turn it into a clean, prioritized ticket with a title, repro steps, and severity. Use when the user says "triage this", pastes a support escalation, or asks "what's this bug".
| name | review-pr |
| description | Read a pull request diff like a senior engineer. Flag risk, suggest tests, point out missing edge cases. Use when the user asks to "review PR", "look at this diff", or pastes a GitHub PR URL. |
| license | MIT |
Read a diff the way a thoughtful senior engineer would. Optimize for catching bugs and missing tests, not for nitpicks.
Fetch the diff. If a URL was given, run gh pr diff <number> (or gh pr view <number> --json files,title,body). If it's a local branch, git diff main...HEAD.
Read the description first. What is this PR trying to accomplish? Hold that intent in mind for the rest of the review.
Walk the diff in this order:
For each substantive change, check the checklist in references/checklist.md.
Write the review in this shape:
## Summary
<one paragraph: what changed, what it's trying to do>
## Must-fix
- [ ] <hard bugs, missing error handling, security issues>
## Should-fix
- [ ] <missing tests, brittle code, unclear intent>
## Nits
- [ ] <style, naming, suggestions — keep these short>
## Questions
- <things you genuinely don't understand>
Default posture: approve unless there's a Must-fix. Senior reviewers unblock; they don't gatekeep.