changelog-generator

Generate standardized Changeset files for automated release documentation.

94|7|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/kobe --skill changelog-generator-sma1lboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Sma1lboy/kobe/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/Sma1lboy/kobe --skill changelog-generator-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of release notes by generating Changeset files, ensuring consistent project documentation and preventing manual errors in the CHANGELOG.

Core Features & Use Cases

  • Standardized Changesets: Automatically creates properly formatted .changeset files that follow the project's strict no-soft-wrap requirements.
  • Release Readiness: Helps maintain a clean, automated release flow by categorizing changes as patch, minor, or major.
  • Use Case: After completing a new feature or bug fix, use this skill to generate the necessary changeset file so the release process can correctly update the project CHANGELOG and GitHub release body.

Quick Start

Ask the assistant to draft a new changeset for the recent changes made to the task pane layout.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate a changeset file for a software release?

To generate a changeset file, you need the Changesets CLI installed. This skill automatically drafts properly formatted .changeset entries categorizing updates as patch, minor, or major for your release documentation.

Why do my automated changelog entries have formatting errors in GitHub releases?

Changelog formatting errors often occur due to soft wraps. This skill generates standardized Changeset files adhering to strict no-soft-wrap requirements, ensuring clean compatibility with GitHub release documentation.

Does the changeset generator require the Changesets CLI to function?

Yes, the changeset generator requires the Changesets CLI as a dependency. You must have it installed and adhere to specific project formatting rules to enable automated changelog management and versioning.

When do I need to create a standardized changeset for my project?

You need to create a standardized changeset after completing a new feature or bug fix. This generates the necessary file for the release process to correctly update the project CHANGELOG and GitHub release body.

What is the best way to automate release notes for kobe deployments?

The best way to automate release notes for kobe deployments is generating standardized Changeset files. This prevents manual errors in the CHANGELOG and maintains a clean, automated release flow.