CommunityProgramação e Desenvolvimentogithub.com

Revisão de código - orientação para testes

Fornece diretrizes para escrever testes de integração e unitários em mudanças de agente.

O que é Revisão de código - orientação para testes?

Esta skill orienta colaboradores de um agente de IA (como Claude Code, Cursor ou Codex) sobre como criar testes ao modificar a lógica do agente. Ela prioriza testes de integração sobre testes unitários, especialmente quando a mudança afeta o comportamento do usuário ou a lógica central do agente. Os testes de integração devem ser colocados em `core/suite` e utilizar `test_codex` para configurar uma instância de teste. Testes unitários, quando necessários, devem ficar em arquivos dedicados com sufixo `_tests.rs`, evitando funções de teste no código principal. Além disso, a skill recomenda verificar se já existem helpers que podem tornar os testes mais enxutos e legíveis, promovendo boas práticas de desenvolvimento orientado a testes.

Funciona com~Claude Code✓Codex CLI~Cursor

npx skills add https://github.com/openai/codex/tree/main/.codex/skills/code-review-testing

Installed? Explore more Programação e Desenvolvimento skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ver original→Navegar por todas as habilidades

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

Documentação

Para mudanças no agente, prefira testes de integração em vez de testes unitários. Os testes de integração estão em core/suite e usam test_codex para configurar uma instância de teste do codex.

Funcionalidades que alteram a lógica do agente devem incluir um teste de integração:

Forneça uma lista das principais mudanças lógicas e comportamentos visíveis ao usuário que precisam ser testados.

Se testes unitários forem necessários, coloque-os em um arquivo de teste dedicado (*_tests.rs). Evite funções exclusivas para teste na implementação principal.

Verifique se existem helpers já prontos para tornar os testes mais eficientes e legíveis.

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

babysit-pr

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.

code-review

Run a final code review on a pull request

code-review-change-size

Change size guidance (800 lines)

code-review-context

Model visible context

codex-bug

Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.

codex-issue-digest

Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.

codex-pr-body

Update the title and body of one or more pull requests.

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

openai/babysit-pr

openai-docs

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

openai/test-tui

Guide for testing Codex TUI interactively

path-types

Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones.

plugin-creator

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.

pushing-ci-changes

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

remote-tests

Testing against remote executors in integration tests.

skill-creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

test-tui