credit-note-fixer
$
npx mdskill add openai/openai-agents-python/credit-note-fixerCorrect credit-note formatting bugs and rerun targeted tests.
- Resolves output label errors and ensures positive amounts.
- Uses apply_patch with workspace-root-relative file paths.
- Executes sh tests/test_credit_note.sh from the repo directory.
- Delivers a summary of the bug, fix, and verification command.
SKILL.md
.github/skills/credit-note-fixerView on GitHub ↗
--- name: credit-note-fixer description: Fix the tiny credit-note formatting bug and rerun the exact targeted test command. --- # Credit Note Fixer Follow this workflow: 1. Read `repo/task.md`. 2. Inspect `repo/credit_note.sh` and `repo/tests/test_credit_note.sh`. 3. Make the smallest correct change that keeps the output label as `credit` and the amount positive. If you use `apply_patch`, use workspace-root-relative paths such as `repo/credit_note.sh` and `repo/tests/test_credit_note.sh`. 4. Run exactly `sh tests/test_credit_note.sh` from `repo/`. 5. In the final answer, summarize the bug, the fix, and the exact verification command.
More from openai/openai-agents-python
- code-change-verificationRun the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
- 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.