openai/openai-agents-js
Overview
This skill runs the mandatory verification stack whenever changes touch runtime code, tests, or build/test configuration. It ensures dependencies install correctly, the project builds, linting and type checks (including generated declarations) succeed, and all tests pass before work is marked complete. Follow the provided scripted entry points from the project root to run the full sequence with fail-fast behavior.
How this skill works
The skill executes a strict sequence of commands that install packages, build packages, run build-checks across the monorepo, validate generated distributions, run linting, and execute tests. It provides shell and PowerShell wrappers that enforce the correct order and stop immediately on failure so you can fix issues as they arise. Re-running the full stack after fixes confirms issues are resolved.
When to use it
- When code changes affect runtime modules or shared libraries
- When tests were added, modified, or are flaky
- When build configuration, type generation, or bundling behavior changed
- Before marking work complete or opening a final review/merge request
Best practices
- Run the verification from the project root so cross-package checks execute correctly
- Use the provided run scripts to preserve order and fail-fast semantics
- Fix the first failing command, then re-run the full stack rather than skipping steps
- Ensure generated declaration outputs are included in type checks before approving changes
- Run on the same OS/Node version used by CI to reproduce environment-specific failures
Example use cases
- A TypeScript runtime refactor touches multiple packages — run full verification to catch type or build regressions
- Adding or changing tests — validate that test suites pass and type declarations remain correct
- Updating build or bundler config — confirm dist checks and build-check tasks still succeed
- Modifying shared types or generated code — ensure declaration files are generated and pass type checks
FAQ
Use the provided shell script from a Unix-like terminal or the PowerShell script on Windows; both run the same ordered steps and stop on failure.
What if a command fails on my machine but passes in CI?
Match the CI environment: verify Node and package manager versions, OS differences, and rebuild from a clean state. If failures persist, capture and report the failing output for investigation.
Can I skip steps if I know they won’t be affected?
No. The sequence is designed to catch cross-package and generated-output issues; always run the full stack and address failures before confirming completion.
8 skills
This skill ensures runtime code changes pass installation, build, lint, type checks, and tests before marking work complete.
This skill analyzes test coverage results from pnpm test:coverage, identifies gaps, and drafts high-impact test ideas for review.
This skill helps you upgrade pnpm and align CI manifests by updating pnpm versions, packageManager, and workflow pins across your repo.
This skill generates a concise PR title and draft description after substantive code changes, speeding up PR readiness and consistency.
This skill analyzes main branch doc coverage to identify gaps and propose updates for English docs only, with a readiness to report and seek approval.
This skill validates changesets using LLM judgments against diffs, ensuring correct bump level and repository rules.
This skill helps you retrieve authoritative OpenAI API documentation and endpoint schemas using MCP tools, ensuring accurate, up-to-date guidance.
This skill runs integration tests with a local Verdaccio registry, orchestrating setup, publish, and test steps to validate workflows in your repo.
