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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 4.0k
- Forks
- 1.0k
01 前言 Front Matter
- name
- changeset-validation
- description
- 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.
02 资源文件 7
- 参考文档agents/openai.yaml276 B
- 参考文档references/validation-prompt.md4.5 KB
- 脚本scripts/changeset-assign-milestone.mjs6.9 KB
- 脚本scripts/changeset-prompt.mjs14.0 KB
- 脚本scripts/changeset-prompt.test.mjs7.7 KB
- 脚本scripts/changeset-validation-result.mjs1.7 KB
- 脚本scripts/run-fixtures.sh4.9 KB
03 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):
- Run:
pnpm changeset:validate-prompt - Apply the rules from
references/validation-prompt.mdto the generated prompt. - Respond with a JSON verdict containing ok/errors/warnings/required_bump (English-only strings).
CI (Codex Action):
- Run:
pnpm changeset:validate-prompt -- --ci --output .github/codex/prompts/changeset-validation.generated.md - Use
openai/codex-actionwith the generated prompt and JSON schema to get a structured verdict.
Workflow
- Generate the prompt context via
pnpm changeset:validate-prompt. - Apply the rules in
references/validation-prompt.mdto judge correctness. - Provide a clear verdict and required bump (patch/minor/major/none).
- If the changeset needs edits, update it and re-run the validation.
Branch-level changeset rule (do not skip)
- If any
.changeset/*.mdfile 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
04 同仓库更多 Skills
csv-workbench
Analyze CSV files in /mnt/data and return concise numeric summaries.
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
invoice-total-fixer
Use when fixing invoice total calculations in the sandbox quickstart repository.
test-coverage-improver
Measure JS SDK coverage or address measured coverage gaps. Use for coverage audits and metric regressions, not routine test additions.
sensitive-logging-audit
Audit or fix sensitive-data exposure in JS SDK diagnostics, exceptions, logging, and telemetry.
runtime-behavior-probe
Plan and, after explicit approval, execute runtime-behavior probes for local or live integrations. Use only when explicitly invoked to verify behavior that code review and normal tests cannot settle; define a controlled validation matrix, keep disposable JS probes outside tracked paths, and report observed evidence.