
Code Review Testing
- 392 installs
- 104k repo stars
- Updated August 4, 2026
- openai/codex
Test authoring guidance.
About
Test authoring guidance. For agent changes prefer integration tests over unit tests. Integration tests are under `core/suite` and use `test_codex` to set up a test instance of codex.
- For agent changes prefer integration tests over unit tests. Integration tests are under `core/suite` and use `test_codex
- Features that change the agent logic MUST add an integration test:
- Provide a list of major logic changes and user-facing behaviors that need to be tested.
- If unit tests are needed, put them in a dedicated test file (*_tests.rs).
- Avoid test-only functions in the main implementation.
Code Review Testing by the numbers
- 392 all-time installs (skills.sh)
- +24 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #653 of 2,154 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 4, 2026 (Skillselion catalog sync)
code-review-testing capabilities & compatibility
- Capabilities
- for agent changes prefer integration tests over · features that change the agent logic must add an · provide a list of major logic changes and user f · if unit tests are needed, put them in a dedicate
- Use cases
- documentation
What code-review-testing says it does
Test authoring guidance
npx skills add https://github.com/openai/codex --skill code-review-testingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 392 |
|---|---|
| repo stars | ★ 104k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | openai/codex ↗ |
How do I apply code-review-testing using the workflow in its SKILL.md?
Test authoring guidance
Who is it for?
Developers following the code-review-testing skill for the tasks it documents.
Skip if: Tasks outside the code-review-testing scope described in SKILL.md.
When should I use this skill?
User mentions code-review-testing or related triggers from the skill description.
What you get
Working code-review-testing setup aligned with the documented patterns and constraints.
- core/suite integration test
- Behavior coverage checklist
- Optional *_tests.rs unit tests
By the numbers
- Integration tests live under the core/suite directory
- Rust unit tests use the *_tests.rs file naming convention
Files
For agent changes prefer integration tests over unit tests. Integration tests are under core/suite and use test_codex to set up a test instance of codex.
Features that change the agent logic MUST add an integration test:
- Provide a list of major logic changes and user-facing behaviors that need to be tested.
If unit tests are needed, put them in a dedicated test file (*_tests.rs). Avoid test-only functions in the main implementation.
Check whether there are existing helpers to make tests more streamlined and readable.
Related skills
How it compares
Use this skill only inside the openai/codex repo; for general React or API test authoring, pick framework-specific testing skills instead.
FAQ
What does code-review-testing do?
Test authoring guidance
When should I use code-review-testing?
Invoke when Test authoring guidance.
Is code-review-testing safe to install?
Review the Security Audits panel on this page before installing in production.