Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
openai avatar

Code Change Verification

  • 117 installs
  • 3.5k repo stars
  • Updated August 4, 2026
  • openai/openai-agents-js

openai-agents-js mandatory verification stack for runtime, test, and build changes.

About

Mandatory verification skill for openai-agents-js monorepo changes touching runtime code, tests, or build and test configuration. Defines the required command sequence including typecheck, lint, unit tests, and integration checks before PR submission. Ensures contributors do not merge changes that break the pnpm workspace build graph or package exports. Referenced by other skills like pnpm-upgrade as the follow-up when runtime code is modified.

  • Mandatory verification stack for runtime code changes
  • pnpm workspace typecheck lint and test sequence
  • Required before PR submission in openai-agents-js
  • Referenced by other monorepo maintenance skills
  • Covers build and test configuration changes

Code Change Verification by the numbers

  • 117 all-time installs (skills.sh)
  • +4 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #950 of 2,154 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

code-change-verification capabilities & compatibility

Capabilities
run verification stack · typecheck lint test
Use cases
testing · ci cd
npx skills add https://github.com/openai/openai-agents-js --skill code-change-verification

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs117
repo stars3.5k
Last updatedAugust 4, 2026
Repositoryopenai/openai-agents-js

What verification must I run after changing openai-agents-js runtime code?

Run the mandatory verification stack when openai-agents-js changes affect runtime code, tests, or build behavior.

Who is it for?

Contributors modifying runtime code or tests in openai-agents-js monorepo.

Skip if: Docs-only changes with no build or test impact.

When should I use this skill?

Changes affect runtime code, tests, or build/test behavior in openai-agents-js.

What you get

Full verification stack completed with passing typecheck, lint, and tests.

Files

SKILL.mdMarkdownGitHub ↗

Code Change Verification

Overview

Ensure work is only marked complete after installing dependencies, building, linting, type checking (including generated declarations), and tests pass. Use this skill when changes affect runtime code, tests, or build/test configuration.

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. If any command fails, fix the issue, rerun the script, and report the failing output. 5. Confirm completion only when all commands succeed with no remaining issues.

Manual workflow

  • Run from the repository root in these phases: pnpm i, pnpm build, then pnpm -r build-check, pnpm -r -F "@openai/*" dist:check, pnpm lint, and pnpm test.
  • The skill may execute the final validation phase in parallel, but every step above must still pass.
  • Do not skip steps; stop and fix issues immediately when any step fails.
  • Re-run the full stack after applying fixes so the commands execute with the same barriers and coverage.

Resources

scripts/run.sh

  • Executes the full verification sequence (including declaration checks) with fail-fast semantics.
  • Keeps pnpm i and pnpm build as barriers, then runs independent validation steps in parallel.
  • Prefer this entry point to ensure the commands always run from the repo root with the expected fail-fast behavior.

scripts/run.ps1

  • Windows-friendly wrapper that runs the same verification sequence with fail-fast semantics.
  • Use from PowerShell with execution policy bypass if required by your environment.

Related skills

FAQ

When is this mandatory?

When changes affect runtime code, tests, or build and test configuration.

What if only docs changed?

Light verification may suffice; this skill targets runtime and build changes.

Who references this skill?

Other monorepo skills like pnpm-upgrade point here when runtime code is modified.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.