codex-pr-review
0
总安装量
1
周安装量
安装命令
npx skills add https://github.com/lploc94/codex_skill --skill codex-pr-review
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
continue
1
kimi-cli
1
Skill 文档
Codex PR Review
Purpose
Use this skill to run adversarial review on branch changes before merge â covering code quality, PR description, commit hygiene, and scope.
Prerequisites
- Current branch differs from base branch (has commits not in base).
git diff <base>...HEADproduces output.codexCLI is installed and authenticated.codex-reviewskill pack is installed (npx github:lploc94/codex_skill).
Runner
RUNNER="{{RUNNER_PATH}}"
Workflow
- Ask user to choose review effort level:
low,medium,high, orxhigh(default:high). Ask for base branch (discover and validate â see workflow.md). Ask for PR title and description (optional). SetEFFORT. - Gather branch diff, commit log, file stats. Build prompt from
references/prompts.md. - Start round 1 with
node "$RUNNER" start --working-dir "$PWD" --effort "$EFFORT". - Poll with adaptive intervals (Round 1: 60s/60s/30s/15s…, Round 2+: 30s/15s…). After each poll, report specific activities from poll output (e.g. which files Codex is reading, what topic it is analyzing). See
references/workflow.mdfor parsing guide. NEVER report generic “Codex is running” â always extract concrete details. - Parse issue list with
references/output-format.md. - Fix valid code issues; rebut invalid findings with evidence.
- Resume debate via
--thread-iduntilAPPROVEor stalemate. - Return final review summary with PR-level recommendations.
Effort Level Guide
| Level | Depth | Best for |
|---|---|---|
low |
Surface check | Quick sanity check |
medium |
Standard review | Most day-to-day work |
high |
Deep analysis | Important features |
xhigh |
Exhaustive | Critical/security-sensitive |
Required References
- Detailed execution:
references/workflow.md - Prompt templates:
references/prompts.md - Output contract:
references/output-format.md
Rules
- Codex reviews only; it does not edit files.
- Preserve functional intent unless fix requires behavior change.
- Every accepted code issue must map to a concrete code diff.
- PR-level issues (description, commit hygiene, scope) result in recommendations, not code edits.
- If stalemate persists, present both sides and defer to user.