create-changeset

Create changeset markdown files for Ledger Live package changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill create-changeset-ledger-wallet-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-changeset
Source: https://github.com/Ledger-Wallet-LLC/ledgerwallet/tree/main/.cursor/skills/create-changeset
Command: npx skills add https://github.com/Ledger-Wallet-LLC/ledgerwallet --skill create-changeset-ledger-wallet-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creation of changesets to document Ledger Live package changes for releases and PRs, ensuring consistent release notes.

Core Features & Use Cases

  • Create a .changeset/<adjective-noun-verb>.md file (human-readable identifier) with the changeset format used by @changesets/cli.
  • Ensure package names match exactly what's in each package.json.
  • Define the change's impact level (minor, patch, major) and provide a concise description for PRs and releases.

Quick Start

Run changesets add to create a new changeset for a modified package.

Frequently Asked Questions about create-changeset

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

FAQPage Schema
How do I create a changeset for a Ledger Live package update?

To create a changeset, you generate a .changeset/<adjective-noun-verb>.md file mapping exact package.json names to impact levels and descriptions for Ledger Live releases.

Do I need @changesets/cli to format Ledger Live release notes?

Yes, this Skill generates files using the standard changeset format supported by @changesets/cli to ensure consistent release documentation across the Ledger Live monorepo.

What is the standard changeset format for PR workflow in a monorepo?

The standard changeset format maps exact package names to a semantic versioning impact level (minor, patch, or major) alongside a concise human-readable summary for PRs.

How do changesets enforce package naming during release planning?

Changesets enforce package naming by validating that the modified package names in your changeset file match exactly what is defined in each respective package.json entry.

When should I create a changeset for Ledger Live development?

You should create a changeset during release planning, PR documentation, or package updates within the Ledger Live monorepo to accurately record changes for release notes.