What problem does it solve? When reviewing or implementing changes to agent logic, it is easy to ship behavior changes without adequate test coverage or to place tests in the wrong layer. This Skill enforces a consistent testing strategy so every agent logic change is backed by the right kind of test. ## Core Features & Use Cases - Integration-test-first policy: Directs authors to prefer integration tests under core/suite, using test_codex to spin up a test instance of codex. - Mandatory coverage for behavior changes: Requires listing major logic changes and user-facing behaviors that must be tested whenever agent logic changes. - Unit test conventions: When unit tests are needed, they go in dedicated *_tests.rs files, avoiding test-only functions in the main implementation and reusing existing test helpers. - Use Case: During a code review of a pull request that modifies agent behavior, use this Skill to verify the author added integration tests covering each user-facing behavior change. ## Quick Start Review my agent logic changes and tell me which integration tests I need to add under core/suite.
