code-review-testing

Guides integration test authoring for agent logic changes in Rust codebases.

5|1|Updated Jun 26, 2026

Search Tags:#unit tests #testing #code review #integration tests #rust #test coverage #agent logic

Ready to run

npx skills add https://github.com/looooonk/better-codex --skill code-review-testing-looooonk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-testing
Source: https://github.com/looooonk/better-codex/tree/main/.codex/skills/code-review-testing
Command: npx skills add https://github.com/looooonk/better-codex --skill code-review-testing-looooonk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent logic changes often ship without adequate test coverage, or with tests placed in the wrong locations, making regressions hard to catch and code reviews inconsistent. ## Core Features & Use Cases - Integration Test Enforcement: Requires integration tests under `core/suite` using `test_codex` for any change to agent logic. - Unit Test Organization: Directs unit tests into dedicated `*_tests.rs` files and prohibits test-only functions in main implementation code. - Helper Reuse: Encourages checking for existing test helpers to keep tests streamlined and readable. - Use Case: When reviewing a pull request that modifies agent behavior, apply this guidance to produce a list of major logic changes and user-facing behaviors that must be covered by integration tests. ## Quick Start Review my agent logic changes and tell me which integration tests I need to add under core/suite.

Frequently Asked Questions about code-review-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write integration tests for agent logic changes?▼

Place integration tests under core/suite and use test_codex to set up a test instance of codex. Any feature that changes agent logic must add an integration test covering the major logic changes and user-facing behaviors.

When should I prefer integration tests over unit tests?▼

Prefer integration tests for agent changes because they exercise real behavior through a test instance. Reserve unit tests for isolated logic, and only add them when integration coverage is insufficient.

Where should unit tests go in a Rust project?▼

Put unit tests in a dedicated test file named with the *_tests.rs pattern rather than inline in the implementation. Avoid adding test-only functions to the main implementation code.

How do I keep test code readable and maintainable?▼

Check whether existing test helpers are available before writing new setup code. Reusing helpers keeps tests streamlined, reduces duplication, and makes the intent of each test easier to follow.

What must a code review check for agent behavior changes?▼

Verify the change includes integration tests covering all major logic changes and user-facing behaviors. Also confirm unit tests, if any, are isolated in dedicated test files without polluting the implementation.