changeset-validation

Validate changesets against the current branch diff for package coverage.

Updated Aug 23, 2026

Search Tags:#automation #git #validation #diff #ci #pull-request #changeset

Ready to run

npx skills add https://github.com/redacharf/fin-punk --skill changeset-validation-redacharf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changeset-validation
Source: https://github.com/redacharf/fin-punk/tree/main/.agents/skills/changeset-validation
Command: npx skills add https://github.com/redacharf/fin-punk --skill changeset-validation-redacharf

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill validates whether changesets correctly reflect package changes and adhere to repository rules, ensuring consistent release planning.

Core Features & Use Cases

Diff-aware validation: compares the current branch diff against changesets to verify coverage.
CI/PR integration: supports CI contexts and PR bodies to propagate verification results and suggested bumps.
Updating existing changesets: if changesets exist, ensures they cover all changed packages and reflect the latest diff; prompts updates rather than creating new files when appropriate.
Enforced package rules: checks that changes touch only allowed packages and reports unknown package directories.

Quick Start

Run pnpm changeset:validate-prompt to generate the prompt and validate the current branch diff.

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 my current branch diff?▼

To validate changesets against your current branch diff, run pnpm changeset:validate-prompt to generate a prompt that verifies changeset coverage and accuracy. This ensures changeset files correctly reflect package changes in your repository.

What does changeset validation check for in a pull request?▼

Changeset validation in a pull request checks that changesets cover all changed packages, enforces allowed packages, reports unknown package directories, and suggests required version bumps based on the current branch diff.

Can I use this to update existing changeset files instead of creating new ones?▼

Yes, when existing changesets are found, the validation process ensures they cover all changed packages and reflect the latest diff, prompting updates to existing changeset files rather than creating new ones when appropriate.

Does changeset validation work in CI contexts?▼

Yes, changeset validation supports CI contexts and PR bodies to propagate verification results and suggested version bumps. It applies to changes in packages/ or .changeset/ directories to judge correctness.

Why does my changeset validation report unknown package directories?▼

Changeset validation reports unknown package directories because it enforces allowed packages and checks that changes touch only permitted package directories. This ensures changesets adhere to repository rules for consistent release planning.