skills.rest
lowdefy
lowdefyOFFICIAL
Explore all skills by this author →
Website𝕏@lowdefyGitHub

l-changeset

Generate changeset files from Git commits with bump types.

3.0k|186|Updated Oct 1, 2020
Search Tags:#git#changelog#release management#versioning#monorepo#changeset
One-click install
npx skills add https://github.com/lowdefy/lowdefy --skill l-changeset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: l-changeset
Source: https://github.com/lowdefy/lowdefy/tree/main/.claude/skills/l-changeset
Command: npx skills add https://github.com/lowdefy/lowdefy --skill l-changeset

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of changelog entries and version bump files, streamlining the release process for software projects.

Core Features & Use Cases

  • Automated Changelog Generation: Analyzes Git commits to determine appropriate version bumps (patch, minor, major) and generates user-facing descriptions.
  • Package Versioning: Creates .changeset files that define version updates for specific packages within a monorepo.
  • Use Case: After merging a feature branch, use this Skill to automatically generate a feat changeset for the relevant packages, ensuring the changelog accurately reflects the new functionality.

Quick Start

Use the l-changeset skill to generate a patch changeset for the current branch.

Frequently Asked Questions about l-changeset

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

FAQPage Schema
How do I generate a changeset for a monorepo package based on Git commits?▼

To generate a changeset for a monorepo package, this Skill analyzes Git commit messages on a branch to identify affected packages and automatically assign version bump types like patch, minor, or major. It then creates the corresponding changeset file.

How does automated changelog generation determine version bump types from commit messages?▼

Automated changelog generation determines version bump types by parsing Git commit messages for specific keywords like feat, fix, and BREAKING CHANGE. These keywords map to minor, patch, and major version bumps respectively for the affected packages.

Can I manually override the version bump type for a specific package in a changeset?▼

Yes, you can manually override the version bump type for a specific package. While the Skill automatically suggests bump types based on commit history, it fully supports manual overrides to adjust the release versioning as needed.

What's the best way to prevent duplicate changeset files when merging multiple feature branches?▼

To prevent duplicate changeset files, this Skill checks for existing changesets on the branch before generating new ones. This ensures that duplicate version bump entries are avoided during the release management process.

Does changeset generation work without a monorepo setup?▼

Changeset generation primarily targets monorepo environments by identifying affected packages within the workspace, but it can also create version bump files for single-package repositories by analyzing the standard Git commit history.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
JacobLeyJacobLey
9

versioning

Generate per-PR changesets and changelogs for multi-package repositories.

Community
Intermediate
vm0-aivm0-ai
1.1k

commit

Run format, lint, type-check, and test steps before Git commits.

Official
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced