changeset-validation

Validate changesets against the current branch diff and output JSON verdicts.

3.6k|897|Updated May 31, 2025
One-click install
npx skills add https://github.com/openai/openai-agents-js --skill changeset-validation-openai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changeset-validation
Source: https://github.com/openai/openai-agents-js/tree/main/.agents/skills/changeset-validation
Command: npx skills add https://github.com/openai/openai-agents-js --skill changeset-validation-openai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures that changesets accurately reflect the scope of code changes, preventing missing or misleading release notes and enabling consistent changelog generation across the repository.

Core Features & Use Cases

  • Validates that changesets reflect package changes in the current branch diff
  • Considers uncommitted changes to provide a realistic validation context for local workflows
  • Enforces repository policies for release bumps and PR hygiene, including compatibility with CI workflows

Quick Start

Run pnpm changeset:validate-prompt to generate the verdict JSON.

Frequently Asked Questions about changeset-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate changesets against a branch diff before merging a pull request?

Validate changesets against a branch diff using LLM-based judgment to compare modified packages under packages/ or .changeset/ and output a JSON verdict with ok, errors, warnings, and required_bump fields for automated checks.

Can I include uncommitted local changes when verifying changeset compliance?

Yes, changeset validation considers uncommitted local changes to provide a realistic validation context, applying whenever packages under packages/ or .changeset/ are modified during local workflows.

What is LLM-based changeset validation and how does it enforce release bump policies?

LLM-based changeset validation uses artificial intelligence judgment to verify that changesets accurately reflect code scope, preventing missing release notes and enforcing repository policies for bump levels and PR hygiene.

Does changeset validation work with CI workflows for automated pull request checks?

Yes, changeset validation enforces repository policies for release bumps and PR hygiene with compatibility for CI workflows, outputting a JSON object suitable for automated checks.

Why does my changeset validation fail when modifying packages without updating the .changeset directory?

Changeset validation fails because it verifies that changesets accurately reflect the scope of code changes, triggering whenever packages under packages/ or .changeset/ are modified to prevent misleading release notes.