changeset-validation_skill

Overview

This skill validates changesets in the openai-agents-js monorepo by using an LLM to judge git diffs, including uncommitted local changes. It ensures changeset files under .changeset/ and package modifications under packages/ follow repository rules and produce the correct version bump. Use it locally or in CI to generate a structured JSON verdict with ok/errors/warnings/required_bump. The validation logic is driven by a single shared prompt so local and CI reviews are consistent.

How this skill works

The tool gathers context from the current git diff (committed and uncommitted) and the repository tree, then generates a prompt that encodes the validation rules from the shared reference prompt. An LLM evaluates whether each changeset accurately describes the code changes and recommends a required bump level (patch/minor/major/none). The output is a JSON verdict containing ok, errors, warnings, and required_bump suitable for human review or automatic gating in CI.

When to use it

• Before opening or updating a pull request that touches packages/ or .changeset/.
• Locally, to check uncommitted edits and confirm the correct bump before committing.
• In CI to enforce consistent changeset quality and bump rules across contributors.
• When confirming whether experimental or preview-labeled changes can be patch bumps.
• To verify that a PR's changeset complies with repository bump policies before release.

Best practices

• Keep the shared prompt file as the single source of truth for validation rules.
• Run validation locally prior to pushing changes to reduce CI failures.
• Include explicit experimental/preview labels in diffs when intending a smaller bump.
• Treat the LLM verdict as authoritative but review errors/warnings manually when needed.
• Use the generated JSON verdict to gate CI checks or to provide clear reviewer guidance.

Example use cases

• Run locally (pnpm changeset:validate-prompt) to check uncommitted changesets and get an immediate JSON verdict.
• Integrate into GitHub Actions to validate PRs automatically and reject incorrect bump levels.
• Audit a proposed minor feature to ensure it doesn't mistakenly request a major bump.
• Validate that documentation-only edits do not trigger package version bumps.
• Confirm multiple package changes are reflected correctly across their corresponding changesets.