菜单
Use this skill when reviewing a pull request for merge readiness. The goal is to produce a priority-organized assessment that clearly communicates what must be fixed before merge.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill when the user has a rough idea, wants to explore a feature, or says "let's brainstorm" or "help me design." The goal is to refine an idea into a validated design doc before any code is written.
Use this skill when ending a session and you want the next session to pick up where you left off. The goal is to capture enough context for seamless session continuity.
Use this skill when starting feature work that needs isolation from the current workspace, or when you need to work on multiple branches simultaneously. The goal is to create an isolated worktree with a verified clean baseline.
Use this skill when fixing a bug caused by invalid data reaching deep into execution. The goal is to add validation at every layer the data passes through, making the bug structurally impossible to reproduce.
Use this skill when documentation has drifted from the codebase, needs an inventory, or should be archived.
Autonomous implementation pipeline. Reads a plan file, reviews it adversarially,
| name | onex-pr-review |
| description | Use this skill when reviewing a pull request for merge readiness. The goal is to produce a priority-organized assessment that clearly communicates what must be fixed before merge. |
| disable-model-invocation | true |
Use this skill when reviewing a pull request for merge readiness. The goal is to produce a priority-organized assessment that clearly communicates what must be fixed before merge.
Systematically review all PR changes, classify issues by severity, and produce a merge readiness verdict. This ensures consistent review standards and prevents critical issues from reaching production.
gh CLI for gh pr view when you are working against GitHub; if unavailable, use local git diff / Cursor diffs insteadFetch PR context.
Run gh pr view <number> --json title,body,files,reviews,comments to gather the full picture. Read the changed files locally to understand the actual diff.
Review each changed file. For every modified file, check for: correctness, security issues, performance regressions, missing tests, breaking API changes, and code quality.
Classify findings by priority. Assign each finding exactly one severity level:
Assess merge readiness. The PR is merge-ready only when all CRITICAL, MAJOR, and MINOR issues are resolved. NITs do not block merge.
Write the review summary. Output a priority breakdown table, merge readiness verdict, and each finding grouped by severity with file path and description.
A structured review containing: