Agent skill

integration-tests

Run the integration-tests pipeline that depends on a local npm registry (Verdaccio). Use when asked to execute integration tests or local publish workflows in this repo.

Stars 2,570
Forks 665

Install this agent skill to your Project

npx add-skill https://github.com/openai/openai-agents-js/tree/main/.agents/skills/integration-tests

SKILL.md

Integration Tests

Overview

Run integration tests that require a local npm registry by starting pnpm local-npm:start in a background subprocess, executing the build/reset/publish/test pipeline in the main process, then cleanly shutting down the registry process and returning results.

Workflow

1. Start the local registry (subprocess)

  • Start a background process with pnpm local-npm:start and keep its session id so it can be stopped later.
  • Wait until the registry is ready (look for a Verdaccio listen message or the default http://localhost:4873 line). If no explicit ready line appears, wait a few seconds and proceed.
  • If the port is already in use, note that an existing registry may be running and proceed only if it matches the expected local registry; otherwise stop it and restart.

2. Run the main pipeline (main process)

Run this exact sequence in the main process and capture the output:

bash
pnpm i && pnpm build:ci && pnpm local-npm:reset && pnpm local-npm:publish && pnpm test:integration
  • Use pnpm build:ci here so the skill validates the same serialized build path that GitHub Actions now uses, while still running the normal prebuild and postbuild lifecycle steps.

  • Return the full success/failure outcome and a concise summary of the results.

  • Always capture the stdout/stderr from pnpm test:integration and include it in the final response (trim obvious noise if extremely long) inside a fenced code block.

  • Do not use watch mode.

If pnpm local-npm:publish fails

Troubleshoot using integration-tests/README.md, which lists the canonical recovery steps. If time is short, prioritize the fixes in the order given there and surface the exact error text in your response.

3. Clean up the registry process

  • Send Ctrl+C to the registry subprocess and wait for it to exit.
  • If it does not exit, terminate it by PID and confirm the port is free before finishing.

Output expectations

  • Always include the integration test results in the response.
  • If any step fails, include the failing command, the error output summary, and the next recommended action.

Expand your agent's capabilities with these related and highly-rated skills.

openai/openai-agents-js

openai-knowledge

Use 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`.

2,570 665
Explore
openai/openai-agents-js

final-release-review

Perform 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-js.

2,570 665
Explore
openai/openai-agents-js

examples-auto-run

Run examples:start-all in auto mode with parallel execution, per-script logs, and start/stop helpers.

2,570 665
Explore
openai/openai-agents-js

implementation-strategy

Decide how to implement runtime and API changes in openai-agents-js before editing code. Use when a task changes exported APIs, runtime behavior, schemas, 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.

2,570 665
Explore
openai/openai-agents-js

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 (docs/src/content/docs/**) and never touch translated docs under docs/src/content/docs/ja, ko, or zh. Provide a report and ask for approval before editing docs.

2,570 665
Explore
openai/openai-agents-js

pnpm-upgrade

Keep pnpm current: run pnpm self-update/corepack prepare, align packageManager in package.json, and bump pnpm/action-setup + pinned pnpm versions in .github/workflows to the latest release. Use this when refreshing the pnpm toolchain manually or in automation.

2,570 665
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results