create-changeset

Name: create-changeset
Availability: InStock
Author: proofgeist

Generate version bump changesets from git commit history for monorepo packages.

17|5|Updated Sep 24, 2024

Search Tags:#git #release management #versioning #conventional commits #monorepo #changeset

Ready to run

npx skills add https://github.com/proofgeist/proofkit --skill create-changeset-proofgeist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-changeset
Source: https://github.com/proofgeist/proofkit/tree/main/.claude/skills/create-changeset
Command: npx skills add https://github.com/proofgeist/proofkit --skill create-changeset-proofgeist

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of analyzing code changes and generating formal "changesets" required for releasing new versions of packages in a monorepo, ensuring consistent and accurate versioning.

Core Features & Use Cases

Automated Change Analysis: Analyzes git commits to determine the type of version bump (major, minor, patch) based on Conventional Commits.
Changeset File Generation: Creates .changeset/*.md files with appropriate versioning and descriptions.
Linting & Validation: Ensures generated changeset files adhere to quality standards before committing.
Use Case: When you've finished a new feature and are ready to create a pull request, this skill will automatically prepare the necessary files to version and release your changes.

Quick Start

Use the create-changeset skill to prepare a version bump for the latest changes.

Frequently Asked Questions about create-changeset

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

FAQPage Schema

How do I automatically generate changesets for monorepo packages from git commits?▼

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.

How does conventional commits versioning work for monorepo releases?▼

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.

What is the best way to prepare a monorepo version bump before creating a pull request?▼

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.

Can I validate generated changeset files to ensure they meet quality standards before committing?▼

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.

Do I need a specific commit message format to automate changeset generation?▼

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.

What are the limitations of automating changeset generation from git history?▼

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.