changeset

Create Changesets-compatible markdown files for semver intent and changelog entries.

1|Updated Jul 7, 2022
One-click install
npx skills add https://github.com/chiubaka/circleci-orb --skill changeset-chiubaka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/chiubaka/circleci-orb/tree/main/org/agents/skills/changeset
Command: npx skills add https://github.com/chiubaka/circleci-orb --skill changeset-chiubaka

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation and management of Changesets-compatible markdown files, ensuring semver intent, category prefixes, and changelog voice are correctly applied for release notes.

Core Features & Use Cases

  • Changeset Creation: Generate markdown files that declare package bumps and changelog entries.
  • Category Prefixing: Enforce required category prefixes for changelog grouping.
  • Monorepo Type Voice: Match changelog voice to monorepo type (library vs deployable app).
  • Use Case: When adding or editing a changeset, preparing a release-impacting PR, or when the user mentions changesets or package version bumps.

Quick Start

Create a changeset for the package 'my-package' with a patch bump using the 'changeset' skill.

Frequently Asked Questions about changeset

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

FAQPage Schema
How do I automate changeset creation for semver package bumps in a monorepo?

Automating changeset creation for semver package bumps involves generating Changesets-compatible markdown files that declare version intent and changelog entries. This Skill matches changelog voice to your monorepo type, whether library or deployable app.

How do I enforce category prefixes for changelog grouping when using changesets?

Enforcing category prefixes for changelog grouping requires applying specific prefixes to your changeset markdown files. This Skill automates the prefixing process to ensure changelog entries are correctly categorized during release note generation.

Do I need the Changesets CLI installed to manage release notes with this approach?

Yes, you need the Changesets CLI installed and configured to manage release notes with this approach. This Skill automates the creation of Changesets-compatible markdown files but requires the underlying CLI and configuration to function properly.

Can I use this changeset automation for both library and deployable app monorepos?

Yes, you can use this changeset automation for both library and deployable app monorepos. The Skill matches the changelog voice to the specific monorepo type, ensuring appropriate release note formatting for either context.

What is the best way to prepare a release-impacting PR with semver intent declaration?

The best way to prepare a release-impacting PR is to generate a Changesets-compatible markdown file declaring your semver intent. This Skill automates that file creation, ensuring package bumps and changelog entries are correctly formatted.