release-plan

Generates Nx version plan files with patch bumps and one package per file.

23|5|Updated Apr 3, 2025
One-click install
npx skills add https://github.com/LedgerHQ/lumen --skill release-plan-ledgerhq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-plan
Source: https://github.com/LedgerHQ/lumen/tree/main/.claude/skills/release-plan
Command: npx skills add https://github.com/LedgerHQ/lumen --skill release-plan-ledgerhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces consistent Nx release versioning rules in the Lumen monorepo, preventing incorrect bump types and multi-package version plan files that break the release workflow. ## Core Features & Use Cases - Patch-only bump enforcement: Every version plan frontmatter must use patch, never minor or major, regardless of commit type or breaking changes. - One package per file: Changes affecting multiple packages require separate version-plan-<timestamp>-<pkg>.md files, one per package. - Path-to-package mapping: Maps libs/ui-react/, libs/ui-rnative/, libs/design-core/, and libs/utils-shared/ to their published package names. - Use Case: After adding a feature to both the React and React Native Select components, generate two separate version plan files, each declaring a patch bump for its respective package. ## Quick Start Ask the assistant to create an Nx version plan for your changes under libs/ui-react/src, and it will produce a correctly formatted patch-only version plan file.

Frequently Asked Questions about release-plan

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

FAQPage Schema
How do I create an Nx version plan file?▼

Create a markdown file in .nx/version-plans/ named version-plan-<timestamp>-<pkg>.md with frontmatter declaring the package name and bump type, followed by a changelog message. In this repo the bump type must always be patch.

What bump type should I use for a new feature in an Nx release plan?▼

Always use patch, even for feat(...) commits, new components, or breaking changes. Do not infer minor from features or major from breaking changes; the repository enforces patch-only bumps.

Can one version plan file bump multiple packages?▼

No, each version plan file must list exactly one package in its frontmatter. If a change affects N packages, create N separate files, one per package, each with its own patch bump.

When is a version plan required for monorepo changes?▼

A plan is required for any change to production source under libs/*/src/. Files matching ignorePatternsForPlanCheck in nx.json, such as tests, stories, markdown, Figma files, and configs, are exempt.

Which package name maps to libs/ui-react in version plans?▼

The path libs/ui-react/ maps to @ledgerhq/lumen-ui-react. Similarly, libs/ui-rnative/ maps to @ledgerhq/lumen-ui-rnative, libs/design-core/ to @ledgerhq/lumen-design-core, and libs/utils-shared/ to @ledgerhq/lumen-utils-shared.