code-change-verification
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
When & Why to Use This Skill
The Code Change Verification skill is an automated quality assurance tool designed to streamline the Python development workflow. It enforces a mandatory verification stack—including code formatting, linting, static type checking with mypy, and unit testing—to ensure that any changes to runtime code or build configurations meet strict repository standards before being finalized. By providing a 'fail-fast' execution environment, it helps developers identify and resolve regressions and style inconsistencies early in the development cycle.
Use Cases
- Pre-submission Validation: Automatically execute the full suite of linting and tests before marking a coding task as complete to ensure high-quality code delivery.
- Regression Prevention: Run the verification stack after modifying runtime logic to confirm that new changes haven't broken existing functionality.
- Code Style Standardization: Use the integrated formatting and linting tools to maintain consistent code aesthetics and compliance with project-specific style guides.
- Type Safety Checks: Leverage automated mypy execution to catch potential type errors and improve code maintainability during the development process.
| name | code-change-verification |
|---|---|
| description | Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository. |
Code Change Verification
Overview
Ensure work is only marked complete after formatting, linting, type checking, and tests pass. Use this skill when changes affect runtime code, tests, or build/test configuration. You can skip it for docs-only or repository metadata unless a user asks for the full stack.
Quick start
- Keep this skill at
./.codex/skills/code-change-verificationso it loads automatically for the repository. - macOS/Linux:
bash .codex/skills/code-change-verification/scripts/run.sh. - Windows:
powershell -ExecutionPolicy Bypass -File .codex/skills/code-change-verification/scripts/run.ps1. - If any command fails, fix the issue, rerun the script, and report the failing output.
- Confirm completion only when all commands succeed with no remaining issues.
Manual workflow
- If dependencies are not installed or have changed, run
make syncfirst to install dev requirements viauv. - Run from the repository root in this order:
make format,make lint,make mypy,make tests. - Do not skip steps; stop and fix issues immediately when a command fails.
- Re-run the full stack after applying fixes so the commands execute in the required order.
Resources
scripts/run.sh
- Executes the full verification sequence with fail-fast semantics from the repository root. Prefer this entry point to ensure the required commands run in the correct order.
scripts/run.ps1
- Windows-friendly wrapper that runs the same verification sequence with fail-fast semantics. Use from PowerShell with execution policy bypass if required by your environment.