New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Code Change Verification

by openai in openai/openai-agents-js

Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.

OfficialMITAuto-check passedDevelopment

Install Code Change Verification

skills CLI
$ npx skills add openai/openai-agents-js --skill code-change-verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openai/openai-agents-js code-change-verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openai/openai-agents-js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-change-verification .claude/skills/code-change-verification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-change-verification
GitHub stars
3.9k
Token cost
~1.1k tokens
SKILL.md length
541 words
Files
5 (incl. scripts)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.

  • Works in 7 steps: Keep this skill at… → Run the skill in the user's selected… → Codex on macOS/Linux: /usr/bin/env -u… → …
  • Tasks that involve Linting and formatting
  • SKILL.md covers Overview, Quick start, Start condition and host… and Codex execution policy, plus 2 more sections
  • Runs JavaScript, PowerShell and Shell scripts from its folder; calls pnpm and bash; needs OPENAI_API_KEY

What it does

Code Change Verification is an agent skill from openai/openai-agents-js, published by the product's own GitHub organization. Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `agents/openai.yaml` and `scripts/run.sh`).

It sits in Development, covering Linting and formatting. It works with OpenAI. The repository describes itself as: A lightweight, powerful framework for multi-agent workflows and voice agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Linting and formatting

Example prompts

  • “/code-change-verification”

Requirements

  • Node.js
  • A Bash shell
  • PowerShell
  • A credential in OPENAI_API_KEY

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Keep this skill at ./.agents/skills/code-change-verification so it loads automatically for the repository.
  2. Run the skill in the user's selected checkout without changing worktrees or branches.
  3. Codex on macOS/Linux: /usr/bin/env -u OPENAI_API_KEY bash .agents/skills/code-change-verification/scripts/run.sh.
  4. Other macOS/Linux environments: bash .agents/skills/code-change-verification/scripts/run.sh.
  5. Windows: powershell -ExecutionPolicy Bypass -File .agents/skills/code-change-verification/scripts/run.ps1.
  6. If any command fails, fix the issue, rerun the script, and report the failing output.
  7. Confirm completion only when all commands succeed with no remaining issues.

What it can do on your machine

Read from SKILL.md and the folder at commit 05241c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (JavaScript, PowerShell and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • pnpm
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Change Verification loads about 1.1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from openai/openai-agents-js at commit 05241c7, republished under its MIT licence (© openai). 541 words, ~1,053 tokens.

Download SKILL.mdSave it as .claude/skills/code-change-verification/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
code-change-verification
description
Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.

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. This is a post-review final gate: when $implementation-final-review applies, do not invoke the broad stack until its clean-review condition applies to the stable task diff.

Quick start

  1. Keep this skill at ./.agents/skills/code-change-verification so it loads automatically for the repository.
  2. Run the skill in the user's selected checkout without changing worktrees or branches.
  3. Codex on macOS/Linux: /usr/bin/env -u OPENAI_API_KEY bash .agents/skills/code-change-verification/scripts/run.sh.
  4. Other macOS/Linux environments: bash .agents/skills/code-change-verification/scripts/run.sh.
  5. Windows: powershell -ExecutionPolicy Bypass -File .agents/skills/code-change-verification/scripts/run.ps1.
  6. If any command fails, fix the issue, rerun the script, and report the failing output.
  7. Confirm completion only when all commands succeed with no remaining issues.

Start condition and host capacity

  • During iterative review, use only focused tests and a narrowly targeted static check when the changed typing boundary requires one. Defer repository-wide pnpm -r build-check and the rest of this complete stack until review is clean.
  • Immediately before starting the complete stack, use available read-only task or process evidence to check whether another repository-wide test, typecheck, build, examples runner, or integration command is already active on the same host.
  • When concrete contention is visible, continue useful non-heavy work such as review, remediation, evidence preparation, or focused checks, then check again later. Do not create or wait on a repository lock, host-wide mutex, or sentinel file.
  • Start automatically once review is clean, the diff is stable, and observable host capacity is available. Do not require a user-triggered finalize message. If host telemetry is unavailable, do not block solely because capacity cannot be measured.

Codex execution policy

Repository verification and all child processes must remain in the normal Codex workspace sandbox. Never request elevated sandbox permissions for verification, and never retry with broader host access after a failure.

On macOS/Linux, use the exact Codex command from Quick start so an inherited OPENAI_API_KEY is removed before the repository-controlled wrapper starts. Investigate failures inside the workspace sandbox and report any coverage that the sandbox cannot provide instead of weakening the sandbox boundary.

Show full SKILL.md (179 more words)Show less

Manual workflow

  • Run from the repository root in these phases: pnpm i --frozen-lockfile, pnpm build, then pnpm -r build-check, pnpm -r -F "@openai/*" dist:check, pnpm lint, pnpm test, and pnpm format:check:changed.
  • 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.
  • The install intentionally runs without forcing CI or prompt-confirmation settings. If pnpm reports incompatible node_modules, stop and diagnose the configuration mismatch instead of silently recreating dependencies.

Resources

scripts/run.sh
  • Executes the full verification sequence (including declaration checks) with fail-fast semantics.
  • Keeps pnpm i --frozen-lockfile and pnpm build as barriers, then runs the root verify:* scripts in parallel with pnpm.
  • 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.

© openai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts) in .agents/skills/code-change-verification of openai/openai-agents-js.

  • SKILL.md
  • agents/openai.yaml
  • scripts/run.mjs
  • scripts/run.ps1
  • scripts/run.sh

Open the folder on GitHubat commit 05241c7

Compare with similar skills

Code Change Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Change Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Change Verification this skillopenai/openai-agents-js3.9k—~1.1kAutomated safety check: PassMIT
Code Change Verificationopenai/openai-agents-python30k—~1.4kAutomated safety check: PassMIT
Lintroryeckel/wyoming_openai218—~707Automated safety check: PassApache-2.0
Opencode ConfigIgorWarzocha/Opencode-Workflows122—~1.7kAutomated safety check: PassNone
Get API Docs with chubandrewyng/context-hub14k2 repos~775Automated safety check: PassMIT
DeepChat Provider IntegrationThinkInAIXYZ/deepchat6.4k1 repos~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Code Change Verification

    openai/openai-agents-python

    Official

    Run the required final formatting, lint, type, and test checks after eligible SDK changes pass review.

    30k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Lint

    roryeckel/wyoming_openai

    Run all linters (ruff, pyright) and fix issues in a loop until the codebase is clean.

    218 GitHub stars~707 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Opencode Config

    IgorWarzocha/Opencode-Workflows

    Edit opencode.json, AGENTS.md, and config files. An agent skill from IgorWarzocha/Opencode-Workflows.

    122 GitHub stars~1.7k tokensUpdated 8 mo ago
    Agent WorkflowsAuto-check passed

  • Get API Docs with chub

    andrewyng/context-hub

    Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.

    14k GitHub starsUsed in 2 repos~775 tokens
    DevelopmentAuto-check passed

  • DeepChat Provider Integration

    ThinkInAIXYZ/deepchat

    Guides adding an LLM provider to DeepChat through explicit source changes: collect the provider details, pick a transport path and add registry entries and tests.

    6.4k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed

  • LobeHub Alint Rule Set Maintenance

    lobehub/lobehub

    Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.

    83k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from openai/openai-agents-js

All 10 skills in this repo

  • Changeset Validation

    openai/openai-agents-js

    Official

    Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes).

    3.9k GitHub stars~607 tokensUpdated today
    Auto-check passed

  • Pnpm Upgrade

    openai/openai-agents-js

    Official

    Keep pnpm current: preflight the published package and pnpm/action-setup self-installer, update pnpm locally, align packageManager in package.json, and refresh CI pins.

    3.9k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Final Release Review

    openai/openai-agents-js

    Official

    Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.

    3.9k GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Sensitive Logging Audit

    openai/openai-agents-js

    Official

    Audit or fix sensitive-data exposure in JS SDK diagnostics, exceptions, logging, and telemetry.

    3.9k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Runtime Behavior Probe

    openai/openai-agents-js

    Official

    Plan and, after explicit approval, execute runtime-behavior probes for local or live integrations.

    3.9k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

  • Examples Run Analysis

    openai/openai-agents-js

    Official

    Analyze logs and source from a completed repository example run.

    3.9k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Code Change Verification

What does Code Change Verification do?

Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review. Code Change Verification is an agent skill from openai/openai-agents-js, published by the product's own GitHub organization. Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.

When should I use Code Change Verification?

Code Change Verification fits situations like: tasks that involve Linting and formatting.

How do I install Code Change Verification in Claude Code?

Run `npx skills add openai/openai-agents-js --skill code-change-verification -a claude-code`. Or copy the skill folder (.agents/skills/code-change-verification in openai/openai-agents-js) into .claude/skills/code-change-verification in your project. Claude Code loads it when a task matches its description.

How do I install Code Change Verification in Codex?

Run `npx skills add openai/openai-agents-js --skill code-change-verification -a codex`. Or copy the skill folder (.agents/skills/code-change-verification in openai/openai-agents-js) into .agents/skills/code-change-verification in your project. Codex loads it when a task matches its description.

Can I use Code Change Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openai/openai-agents-js --skill code-change-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-change-verification, .gemini/skills/code-change-verification, .github/skills/code-change-verification and .opencode/skills/code-change-verification in your project.

What does Code Change Verification need to run?

Going by SKILL.md and its folder, Code Change Verification needs JavaScript, PowerShell and a shell for the scripts in its folder, the command-line tools its instructions call (pnpm and bash) and credentials named OPENAI_API_KEY. Our summary lists: Node.js; A Bash shell; PowerShell; A credential in OPENAI_API_KEY.

Does Code Change Verification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Change Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Code Change Verification use?

Code Change Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Change Verification use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Change Verification?

Skills that share tags, products or a category with Code Change Verification: Code Change Verification (openai/openai-agents-python, 30k stars), Lint (roryeckel/wyoming_openai, 218 stars), Opencode Config (IgorWarzocha/Opencode-Workflows, 122 stars) and Get API Docs with chub (andrewyng/context-hub, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Change Verification?

openai (a GitHub organization, an official publisher) maintains it in openai/openai-agents-js, which has 3,898 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

Source: openai/openai-agents-js on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.