From f9045c41fc21747899eac7cca5b38ce1691cbe69 Mon Sep 17 00:00:00 2001
From: juston <96567547+justonf@users.noreply.github.com>
Date: Wed, 5 Nov 2025 14:31:52 -0500
Subject: [PATCH 1/3] update wording
---
examples/codex/build_code_review_with_codex_sdk.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/codex/build_code_review_with_codex_sdk.md b/examples/codex/build_code_review_with_codex_sdk.md
index 4f261357f2..398b37c2b2 100644
--- a/examples/codex/build_code_review_with_codex_sdk.md
+++ b/examples/codex/build_code_review_with_codex_sdk.md
@@ -4,7 +4,7 @@ With [Code Review](https://chatgpt.com/codex/settings/code-review) in Codex Clou
Luckily, we can replicate Codex's cloud hosted review process in our own CI/CD runners. In this guide, we'll build our own Code Review action using the Codex CLI headless mode with both GitHub Actions and Jenkins.
-To build our own Code review, we'll take the following steps:
+To build our own Code review, we'll take the following steps and ahdere to them closely:
1. Install the Codex CLI in our CI/CD runner
2. Prompt Codex in headless (exec) mode with the Code Review prompt that ships with the CLI
@@ -12,7 +12,7 @@ To build our own Code review, we'll take the following steps:
4. Parse the JSON result and use it to make API calls to our SCM to create review comments
Once implemented, Codex will be able to leave inline code review comments:
-
+``
## The Code Review Prompt
From 5c142e096f50522d35a97e86bbf6db7b9174a17a Mon Sep 17 00:00:00 2001
From: juston <96567547+justonf@users.noreply.github.com>
Date: Wed, 5 Nov 2025 16:49:12 -0500
Subject: [PATCH 2/3] update AGENTS.md with priorities
---
AGENTS.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/AGENTS.md b/AGENTS.md
index 5fde1d7798..aba048b509 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -31,6 +31,7 @@ New or relocated content must have an entry in `registry.yaml` with an accurate
## Review Guidelines
+These are considered priority 0 issues for this repo, in addition to the normal priority for possible issues.
- Verify file, function, and notebook names follow the repo's naming conventions and clearly describe their purpose.
- Scan prose and markdown for typos, broken links, and inconsistent formatting before approving.
- Check that code identifiers remain descriptive (no leftover placeholder names) and that repeated values are factored into constants when practical.
From c20c8de9b4cb0b208073c604fee0d2ae7b58bfde Mon Sep 17 00:00:00 2001
From: juston <96567547+justonf@users.noreply.github.com>
Date: Wed, 5 Nov 2025 16:56:51 -0500
Subject: [PATCH 3/3] Fix typos in Codex review guide
---
examples/codex/build_code_review_with_codex_sdk.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/codex/build_code_review_with_codex_sdk.md b/examples/codex/build_code_review_with_codex_sdk.md
index 398b37c2b2..b5a8a909d9 100644
--- a/examples/codex/build_code_review_with_codex_sdk.md
+++ b/examples/codex/build_code_review_with_codex_sdk.md
@@ -4,7 +4,7 @@ With [Code Review](https://chatgpt.com/codex/settings/code-review) in Codex Clou
Luckily, we can replicate Codex's cloud hosted review process in our own CI/CD runners. In this guide, we'll build our own Code Review action using the Codex CLI headless mode with both GitHub Actions and Jenkins.
-To build our own Code review, we'll take the following steps and ahdere to them closely:
+To build our own Code review, we'll take the following steps and adhere to them closely:
1. Install the Codex CLI in our CI/CD runner
2. Prompt Codex in headless (exec) mode with the Code Review prompt that ships with the CLI
@@ -12,7 +12,7 @@ To build our own Code review, we'll take the following steps and ahdere to them
4. Parse the JSON result and use it to make API calls to our SCM to create review comments
Once implemented, Codex will be able to leave inline code review comments:
-``
+
## The Code Review Prompt