test-coverage-improver

Improve test coverage in the OpenAI Agents Python repository: run `make coverage`, inspect coverage artifacts, identify low-coverage files, propose high-impact tests, and confirm with the user before writing tests.

Jump to install

Repository: openai/openai-agents-python
Last source activity: March 20, 2026 at 03:56
Detected SKILL.md language: English
Stars: 28,574
Forks: 4,481

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/openai/openai-agents-python --skill test-coverage-improver

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

docs-sync

Analyze 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.

2026-08-13

implementation-final-review

Perform a risk-tiered zero-base final review loop before an implementation is declared complete. Use only when the user explicitly invokes $implementation-final-review or repository instructions authorize automatic invocation after implementation. Audit the complete merge-base diff for requirement fit, contract-surface coverage, await-boundary and lifecycle gaps, released compatibility, security, protocol, and persistence boundaries, unnecessary complexity, package and generated public surfaces, and adversarial test coverage; use compact self-contained reviewer packets and two concurrent no-history independent reviewers per round, defer broad final repository verification until review is clean and observable host capacity is available, preserve clean evidence for unchanged semantic components, close repeated root-cause groups instead of accumulating local patches, and enforce bounded review cycles in one task-global ledger.

2026-08-11

implementation-kickoff

Start and carry an explicitly invoked openai-agents-python implementation through a fresh isolated worktree and a local PR-ready handoff. Fetch the latest origin/main, keep task changes uncommitted, replay them onto the latest main before final review, run applicable verification and $implementation-final-review, use $pr-draft-summary to generate the complete PR draft and branch name, then create one clean local commit with takeover provenance when applicable. Use only when the user explicitly invokes this skill; never push, open a PR, or mutate GitHub.

2026-08-11

View all from this repository

Test Coverage Improver

Overview

Use this skill whenever coverage needs assessment or improvement (coverage regressions, failing thresholds, or user requests for stronger tests). It runs the coverage suite, analyzes results, highlights the biggest gaps, and prepares test additions while confirming with the user before changing code.

Quick Start

From the repo root run make coverage to regenerate .coverage data and coverage.xml.

Collect artifacts: .coverage and coverage.xml, plus the console output from coverage report -m for drill-downs.

Summarize coverage: total percentages, lowest files, and uncovered lines/paths.

Draft test ideas per file: scenario, behavior under test, expected outcome, and likely coverage gain.

Ask the user for approval to implement the proposed tests; pause until they agree.

After approval, write the tests in tests/, rerun make coverage, and then run $code-change-verification before marking work complete.

Workflow Details

Run coverage: Execute make coverage at repo root. Avoid watch flags and keep prior coverage artifacts only if comparing trends.

Parse summaries efficiently:

Prefer the console output from coverage report -m for file-level totals; fallback to coverage.xml for tooling or spreadsheets.
Use uv run coverage html to generate htmlcov/index.html if you need an interactive drill-down.

Prioritize targets:

Public APIs or shared utilities in src/agents/ before examples or docs.
Files with low statement coverage or newly added code at 0%.
Recent bug fixes or risky code paths (error handling, retries, timeouts, concurrency).

Design impactful tests:

Hit uncovered paths: error cases, boundary inputs, optional flags, and cancellation/timeouts.
Cover combinational logic rather than trivial happy paths.
Place tests under tests/ and avoid flaky async timing.

Coordinate with the user: Present a numbered, concise list of proposed test additions and expected coverage gains. Ask explicitly before editing code or fixtures.

After implementation: Rerun coverage, report the updated summary, and note any remaining low-coverage areas.

Notes

Keep any added comments or code in English.

Do not create scripts/, references/, or assets/ unless needed later.

If coverage artifacts are missing or stale, rerun pnpm test:coverage instead of guessing.