Agent skill

changeset-validation

Validate changesets in openai-agents-js using LLM judgment against git diffs (including uncommitted local changes). Use when packages/ or .changeset/ are modified, or when verifying PR changeset compliance and bump level.

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/changeset-validation

SKILL.md

Changeset Validation

Overview

This skill validates whether changesets correctly reflect package changes and follow the repository rules. It relies on the shared prompt in references/validation-prompt.md so local Codex reviews and GitHub Actions share the same logic. Experimental or preview-only feature additions that are explicitly labeled as such in the diff may remain a patch bump when they do not change existing behavior. Major bumps are only allowed after the first major release; before that, do not use major bumps for feature-level changes.

Quick start

Local (Codex-driven):

  1. Run:
    bash
    pnpm changeset:validate-prompt
    
  2. Apply the rules from references/validation-prompt.md to the generated prompt.
  3. Respond with a JSON verdict containing ok/errors/warnings/required_bump (English-only strings).

CI (Codex Action):

  1. Run:
    bash
    pnpm changeset:validate-prompt -- --ci --output .github/codex/prompts/changeset-validation.generated.md
    
  2. Use openai/codex-action with the generated prompt and JSON schema to get a structured verdict.

Workflow

  1. Generate the prompt context via pnpm changeset:validate-prompt.
  2. Apply the rules in references/validation-prompt.md to judge correctness.
  3. Provide a clear verdict and required bump (patch/minor/major/none).
  4. If the changeset needs edits, update it and re-run the validation.

Branch-level changeset rule (do not skip)

  • If any .changeset/*.md file is already present in the current branch diff, treat it as the active changeset. Do not add a new changeset file.
  • Instead, update the existing changeset file by rewriting its summary to reflect the primary change relative to main. Do not try to capture every incremental update.
  • Keep the summary at one line; replace the line as needed rather than appending. If you must include multiple points, compress them into a single line.

Shared source of truth

  • Keep the prompt file as the single source of validation rules.
  • Keep the script lightweight: it should only gather context and emit the prompt.

Resources

  • references/validation-prompt.md

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