DOWNLOADABLE CODEX SKILL · v1.0.0
Review a pull request for concrete regressions, missing checks, and maintainability risks.
By Abdessalam · Updated
THE WORKFLOW
Review a pull request for concrete regressions, missing checks, and maintainability risks. It keeps the work tied to evidence and the project’s actual constraints.
The user asks Codex to review a branch, commit, diff, or pull request. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-pull-request-review Review this pull request for regressions and give each finding a reproducible trigger.A concise, prioritized review with evidence and explicit coverage limits.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-pull-request-review/SKILL.mdOpen the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.
Open the project in Codex CLI. Use /skills or $aboutcodex-pull-request-review to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-pull-request-review to select the skill explicitly.
Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.
After selecting the skill, use this inspection request:
Read the aboutcodex-pull-request-review skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation
aboutcodex-pull-request-review/SKILL.md1 KBaboutcodex-pull-request-review/references/NOTES.md440 Baboutcodex-pull-request-review/LICENSE.txt1 KB---
name: "aboutcodex-pull-request-review"
description: "Review a pull request for concrete regressions, missing checks, and maintainability risks. Use when the user asks Codex to review a branch, commit, diff, or pull request."
---
# Review a pull request
Review a pull request for concrete regressions, missing checks, and maintainability risks.
## Workflow
1. Read project instructions and establish the intended behavior from the request and changed tests.
2. Inspect the diff in context, following changed values into their callers, consumers, and persistence boundaries.
3. Prioritize reproducible correctness, security, data-loss, and compatibility defects over style preferences.
4. Run focused checks when authorized and feasible; never infer a pass from a test file alone.
5. Report only actionable findings with location, trigger, impact, and a reasonable correction.
Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.
## Deliverable
A concise, prioritized review with evidence and explicit coverage limits. State material limitations and link to changed files or rendered evidence when available.
Does not replace specialist security, legal, or production review. Unavailable dependencies can limit verification.
Structure checked · 2026-09-10
Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.
Package checks confirm file structure. They do not establish that a skill works well on every task.
1.0.0 — Initial instruction-only release with supporting review notes.
Progress stays in this browser. No account needed.
Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.
What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.
THE ABOUTCODEX BRIEFING
One workflow to try, one change explained, and one resource to keep. Planned weekly.
Read the sample issue ↗Confirm your email to join. Unsubscribe anytime through a delivered newsletter. Privacy policy.