MCPInstall

code-review-testing

Test authoring guidance

Installs
634
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/openai/codex --skill code-review-testing
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads code-review-testing automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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.

FAQ

What does the code-review-testing skill do?

Test authoring guidance

How do I install code-review-testing?

Run npx skills add https://github.com/openai/codex --skill code-review-testing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/code-review-testing/ (personal) or .claude/skills/code-review-testing/ (project).

Which AI agents can use code-review-testing?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is code-review-testing safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains code-review-testing?

It is published by openai in openai/codex, and it is an official skill from the maker of the technology it covers. It has 634 recorded installs.

More from openai/codex

View all →

babysit-pr

openai/codex

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

OfficialCode Quality & Workflow4.2K installs

test-tui

openai/codex

Guide for testing Codex TUI interactively

OfficialTesting & QA2.8K installs

code-review

openai/codex

Run a final code review on a pull request

OfficialCode Quality & Workflow748 installs

codex-pr-body

openai/codex

Open the skill to read its SKILL.md instructions.

OfficialCode Quality & Workflow463 installs

Open the skill to read its SKILL.md instructions.

OfficialCode Quality & Workflow450 installs

Open the skill to read its SKILL.md instructions.

OfficialCode Quality & Workflow437 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.