// Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
Decide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewritten directly.
Run python examples in auto mode with logging, rerun helpers, and background control.
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
Build a concise prior authorization packet from local case files and payer policy docs.
Use when the task requires capturing or automating a real browser from the terminal.
Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use in the final handoff after moderate-or-larger changes to runtime code, tests, examples, build/test configuration, or docs with behavior impact; skip only for trivial or conversation-only tasks, repo-meta/doc-only tasks without behavior impact, or when the user explicitly says not to include the PR draft block.
| 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. |
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.
./.agents/skills/code-change-verification so it loads automatically for the repository.bash .agents/skills/code-change-verification/scripts/run.sh.powershell -ExecutionPolicy Bypass -File .agents/skills/code-change-verification/scripts/run.ps1.make format first, then run make lint, make typecheck, and make tests in parallel with fail-fast semantics.make sync first to install dev requirements via uv.make format first, then make lint, make typecheck, and make tests.make lint, make typecheck, and make tests after make format completes, but you must stop the remaining steps as soon as one fails.make format first, then runs make lint, make typecheck, and make tests in parallel with fail-fast semantics from the repository root. It also emits periodic heartbeat updates while the parallel steps are still running. Prefer this entry point to preserve the required ordering while reducing total runtime.make format first and the remaining steps in parallel with fail-fast semantics, plus periodic heartbeat updates while work is still running. Use from PowerShell with execution policy bypass if required by your environment.