skills.rest
getlien
getlienOFFICIAL
Explore all skills by this author →
GitHub

changeset

Analyze Git commits to generate structured changeset files for package versioning.

2|Updated Nov 20, 2025
Search Tags:#automation#git#changelog#versioning#commits#release
One-click install
npx skills add https://github.com/getlien/lien --skill changeset-getlien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changeset
Source: https://github.com/getlien/lien/tree/main/.claude/skills/changeset
Command: npx skills add https://github.com/getlien/lien --skill changeset-getlien

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of analyzing code commits, determining the impact on different packages, and generating a structured changelog file to trigger release workflows.

Core Features & Use Cases

  • Commit Analysis: Identifies and categorizes commits based on conventional commit standards (feat, fix, BREAKING, etc.).
  • Package Impact Assessment: Determines which packages (@liendev/core, @liendev/lien) are affected by the changes.
  • Version Bump Calculation: Calculates the appropriate version bump (patch, minor, major) based on commit types.
  • Changelog Generation: Creates a .changeset/<version-name>.md file in the correct format for automated releases.

Quick Start

Use the changeset skill to prepare the next release by analyzing commits since the last tag.

Frequently Asked Questions about changeset

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

FAQPage Schema
How do I generate a changelog from Git commits for package versioning?▼

To generate a changelog from Git commits, analyze the commit history to categorize changes, determine affected packages, calculate version bumps, and output a structured changeset file for release automation.

How does conventional commit analysis determine version bumps?▼

Conventional commit analysis determines version bumps by identifying commit types like feat, fix, or BREAKING, translating them into patch, minor, or major version increments to prepare the release.

Do I need Git installed to automate release changelog generation?▼

Yes, you need Git installed to automate release changelog generation, because the process retrieves commit logs and performs diff analysis directly through Git operations to assess package impact.

What is the best way to automate package impact assessment for a release?▼

The best way to automate package impact assessment is to analyze Git commit history against your codebase, identifying which specific packages are affected and formatting the results into a changeset file.

Can I create a changeset file manually or should I automate it from commit logs?▼

You can automate changeset file creation by retrieving Git logs and diffs, which categorizes conventional commits, evaluates package impact, calculates version bumps, and formats changelog entries with PR numbers automatically.

Why are some version bumps calculated as major instead of minor?▼

Version bumps are calculated as major instead of minor when the Git commit analysis detects BREAKING changes in the history, whereas feat and fix commits typically trigger minor and patch bumps respectively.

Related Skills

Explore More Software Engineering Skills→
azeemigiazeemigi

release-notes

Generate markdown release notes from Git commits and pull requests.

Community
Advanced
ethan-krichethan-krich
7

changesets

Coordinate semver versioning and changelog generation for multi-package monorepos.

Community
Intermediate
Veloxia-agencyVeloxia-agency

changelog-generator

Generate markdown or JSON changelog entries from Conventional Commit histories.

Community
Advanced
nvimcraftnvimcraft

git-release

Generate release version recommendations and changelog drafts from Git history.

Community
Advanced