changeset-validation

To validate code changesets against git diffs, this skill uses LLM judgment to check if package modifications align with changeset files and determines the correct version bump level. It integrates directly into CI/CD pipelines and local workflows for consistent change management.

You can automate changeset validation in GitHub Actions by integrating this skill to verify pull request compliance. It checks that .changeset files accurately describe code impacts and determine the appropriate version bump before merging any package modifications.

You need to validate changeset files for version bumps before merging a pull request that modifies code in multiple packages. This ensures the generated changeset summaries accurately reflect package modifications and adhere to repository rules to prevent release errors.

Yes, you can use this changeset validation skill with local development workflows by running pnpm changeset:validate-prompt. This generates a validation prompt for review, ensuring package changes align with the generated changeset summaries before committing.

The best way to determine the correct version bump level for package modifications is using LLM judgment to validate changesets against git diffs. This approach evaluates whether the bump should be patch, minor, major, or none based on actual repository rule adherence.

Changeset validation fails when .changeset files do not accurately describe the impact of package modifications or determine the wrong version bump. Using LLM judgment against git diffs catches these mismatches to prevent versioning and release errors.