code-change-verification
$
npx mdskill add openai/openai-agents-python/code-change-verificationRun mandatory verification stack for code, test, or build changes in the OpenAI Agents Python repository.
- Ensures work is complete only after formatting, linting, type checking, and tests pass.
- Integrates with a Makefile for commands like format, lint, typecheck, and tests.
- Decides to execute based on changes affecting runtime code, tests, or build configuration.
- Presents results with periodic heartbeat updates and reports failing output for fixes.
SKILL.md
.github/skills/code-change-verificationView on GitHub ↗
--- 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 1. Keep this skill at `./.agents/skills/code-change-verification` so it loads automatically for the repository. 2. macOS/Linux: `bash .agents/skills/code-change-verification/scripts/run.sh`. 3. Windows: `powershell -ExecutionPolicy Bypass -File .agents/skills/code-change-verification/scripts/run.ps1`. 4. The scripts run `make format` first, then run `make lint`, `make typecheck`, and `make tests` in parallel with fail-fast semantics. 5. While the parallel steps are still running, the scripts emit periodic heartbeat updates so you can tell that work is still in progress. 6. If any command fails, fix the issue, rerun the script, and report the failing output. 7. Confirm completion only when all commands succeed with no remaining issues. ## Manual workflow - If dependencies are not installed or have changed, run `make sync` first to install dev requirements via `uv`. - Run from the repository root with `make format` first, then `make lint`, `make typecheck`, and `make tests`. - Do not skip steps; stop and fix issues immediately when a command fails. - If you run the steps manually, you may parallelize `make lint`, `make typecheck`, and `make tests` after `make format` completes, but you must stop the remaining steps as soon as one fails. - Re-run the full stack after applying fixes so the commands execute in the required order. ## Resources ### scripts/run.sh - Executes `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. ### scripts/run.ps1 - Windows-friendly wrapper that runs the same sequence with `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.
More from openai/openai-agents-python
- credit-note-fixerFix the tiny credit-note formatting bug and rerun the exact targeted test command.
- csv-workbenchAnalyze CSV files in /mnt/data and return concise numeric summaries.
- docs-syncAnalyze main branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/. Use when asked to audit doc coverage, sync docs with code, or propose doc updates/structure changes. Only update English docs under docs/** and never touch translated docs under docs/ja, docs/ko, or docs/zh. Provide a report and ask for approval before editing docs.
- examples-auto-runRun python examples in auto mode with logging, rerun helpers, and background control.
- final-release-reviewPerform a release-readiness review by locating the previous release tag from remote tags and auditing the diff (e.g., v1.2.3...<commit>) for breaking changes, regressions, improvement opportunities, and risks before releasing openai-agents-python.
- implementation-strategyDecide 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.
- openai-knowledgeUse when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
- playwrightUse when the task requires capturing or automating a real browser from the terminal.
- pr-draft-summaryCreate 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.
- prior-auth-packet-builderBuild a concise prior authorization packet from local case files and payer policy docs.