SpyBara
Go Premium

use-cases/github-code-reviews.md 2026-07-20 23:01 UTC to 2026-07-21 22:02 UTC

12 added, 7 removed.

2026
Fri 24 15:00 Thu 23 21:57 Wed 22 20:02 Tue 21 22:02 Mon 20 23:01 Fri 17 22:57 Thu 16 20:57 Wed 15 19:58 Tue 14 17:03 Wed 8 02:01 Mon 6 22:58

name: Review GitHub pull requests tagline: Catch regressions and potential issues before human review. summary: Use Codex code review in GitHub to automatically surface regressions, missing tests, and documentation issues directly on a pull request. skills:

  • token: $security-best-practices url: https://github.com/openai/skills/tree/main/skills/.curated/security-best-practices description: Focus the review on risky surfaces such as secrets, auth, and dependency changes. bestFor:
  • Teams that want another review signal before human merge approval
  • Large codebases for projects in production starterPrompt: title: Ask Codex to review a pull request body: "@codex review for security regressions, missing tests, and risky behavior changes." suggestedModel: cloud relatedLinks:
  • label: Codex code review in GitHub url: /codex/third-party/github
  • label: Custom instructions with AGENTS.md url: /codex/agent-configuration/agents-md

How to use

Start by adding Codex code review to your GitHub organization or repository. See Codex code review in GitHub for more details.

You can set up Codex to automatically review every pull request, or you can request a review with @codex review in a pull request comment.

If Codex flags a regression or potential issue, you can ask it to fix it by commenting on the pull request with a follow-up prompt like @codex fix it.

This will start a new cloud chat that will fix the issue and update the pull request.

Define review guidance

To customize what Codex reviews, add a ## Code Review Rules section to the AGENTS.md closest to the code the rules govern. For example:

## Code Review Rules

### Experiment cohorts

- Do not filter treatment comparisons on post-exposure behavior, including conversion or retention.
  Safe path: build cohorts from assignment or exposure; report conversion as an outcome.

Put repository-wide rules in the root AGENTS.md and service-specific rules in a nested file. Keep rules concise, describe the behavior to flag and any safe path or exception, and leave formatting and lint checks in CI. See Customize what Codex reviews for setup and rule-writing guidance.