# Codex Features and Practical Usage 🔍 Open a PR and get back only the genuinely serious findings, not noise. Codex's GitHub integration posts automated code reviews scoped to high-priority P0/P1 risks. 🏷️ Title: PR Review (@/codex review) 🔗 URL: 📘 Overview Codex's GitHub integration has the AI review a pull request's diff and post high-signal feedback. By design it filters to only P0 and P1 issues, so review comments stay focused on high-priority risks instead of drowning you in nitpicks. ⚙️ How It Works ・For a manual review, comment `@/codex review` on the PR. Codex reacts with 👀 and then posts a GitHub code review. ・Enable Automatic reviews in settings and a review runs the moment a PR is opened, with no mention required. ・Steer the review with a "Review guidelines" section in a top-level `AGENTS.md`. Codex applies the closest `AGENTS.md` to each changed file, so you can nest deeper instructions for package-level scrutiny. ・Mentioning `@/codex` with anything other than `review` kicks off a cloud task using the PR as context, e.g. `@/codex fix the CI failures`. 🛠️ Practical Usage ・First enable the Code review toggle for your repo in the settings (Codex cloud setup is a prerequisite). ・To lock in your review lens, add a "Review guidelines" section to `AGENTS.md` with rules like "Don't log PII" and "Verify authentication middleware wraps every route." ・For a one-off focus, append it inline: `@/codex review for security regressions`. ・To go from review straight to a fix, comment `@/codex fix the P1 issue` and Codex starts a cloud task to address it. 💡 Use Cases On a team where reviewers are stretched thin, let Codex do a first pass to clear P0/P1 issues before human review, cutting down review round-trips. Codify non-negotiable concerns like security and PII handling in `AGENTS.md` so every PR is checked for them automatically. ⚠️ Caveats ・Requires Codex cloud setup on the repo and code review enabled for it. ・The manual trigger must be the exact string `@/codex review`. ・Automatic reviews depend on the toggle being configured correctly, so verify settings during onboarding. #OpenAICodex# #CodeReview#