create-changeset

To generate changesets for monorepo packages, this skill analyzes git commit history to determine version bumps and creates `.changeset/*.md` files with appropriate versioning and descriptions automatically.

Conventional commits versioning determines major, minor, or patch version bumps by parsing commit messages. This skill uses that mechanism to map specific commit types to appropriate version increments for each monorepo package.

The best way to prepare a monorepo version bump is to run this skill after finishing a feature; it automatically prepares the necessary changeset files to version and release your changes alongside your pull request.

Yes, you can validate generated changeset files using textlint. This skill ensures the created `.changeset/*.md` files adhere to quality standards through linting and validation before you commit them.

Yes, you need to use Conventional Commits formatting in your git history. This skill relies on parsing those structured commit messages to determine whether a major, minor, or patch version bump is required.

Automating changeset generation depends entirely on strict adherence to Conventional Commits; non-standard or poorly formatted commit messages will prevent the skill from accurately determining the correct version bump or generating valid changeset files.