changeset-validation

1---2name: changeset-validation3description: 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.4---5 6# Changeset Validation7 8## Overview9 10This 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.11Experimental 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.12Major bumps are only allowed after the first major release; before that, do not use major bumps for feature-level changes.13 14## Quick start15 16Local (Codex-driven):17 181. Run:19   ```bash20   pnpm changeset:validate-prompt21   ```222. Apply the rules from `references/validation-prompt.md` to the generated prompt.233. Respond with a JSON verdict containing ok/errors/warnings/required_bump (English-only strings).24 25CI (Codex Action):26 271. Run:28   ```bash29   pnpm changeset:validate-prompt -- --ci --output .github/codex/prompts/changeset-validation.generated.md30   ```312. Use `openai/codex-action` with the generated prompt and JSON schema to get a structured verdict.32 33## Workflow34 351. Generate the prompt context via `pnpm changeset:validate-prompt`.362. Apply the rules in `references/validation-prompt.md` to judge correctness.373. Provide a clear verdict and required bump (patch/minor/major/none).384. If the changeset needs edits, update it and re-run the validation.39 40## Branch-level changeset rule (do not skip)41 42- 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.**43- 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.44- 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.45 46## Shared source of truth47 48- Keep the prompt file as the single source of validation rules.49- Keep the script lightweight: it should only gather context and emit the prompt.50 51## Resources52 53- `references/validation-prompt.md`54