The best way to control Claude Code, Codex and more from any computer or phone
| 1 | --- |
| 2 | title: Test Signal |
| 3 | model: gpt-6-1-terra |
| 4 | reasoning: low |
| 5 | input: incremental |
| 6 | tools: |
| 7 | - browse_code |
| 8 | - modify_pr |
| 9 | # An explicit include overrides ignore.md, which skips test files for every other check. |
| 10 | include: |
| 11 | - "**/*.test.*" |
| 12 | exclude: |
| 13 | - ".repos/**" |
| 14 | requires: |
| 15 | - Check |
| 16 | maxBudgetPerRun: 1 |
| 17 | maxBudgetPerPR: 5 |
| 18 | conclusion: neutral |
| 19 | --- |
| 20 | |
| 21 | # Test signal review |
| 22 | |
| 23 | Review only the tests this pull request adds or grows. Tests it moves, renames, or deletes are not findings. The rules are in `docs/internals/testing.md` under `## What to test`; read that section first and hold new tests to it. |
| 24 | |
| 25 | Post each finding as a brief inline comment on the new test with one fix. Ask only for fewer or smaller tests, never for more coverage. |
| 26 | |
| 27 | When there are no findings, make the entire final response exactly `All clear` on one line with nothing else. |