changeset-discipline

Filter internal implementation details from software release notes.

3|2|Updated May 12, 2026

Search Tags:#automation #changelog #release management #versioning #documentation #changesets

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill changeset-discipline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changeset-discipline
Source: https://github.com/kriscendobot/garden/tree/main/skills/changeset-discipline
Command: npx skills add https://github.com/kriscendobot/garden --skill changeset-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents noisy, unhelpful changelogs by enforcing strict criteria on when and how to document changes, ensuring that downstream users only see information relevant to their upgrade decisions.

Core Features & Use Cases

Change Filtering: Automatically identifies which code changes warrant a changeset entry and which are internal hygiene that should be ignored.
Standardized Documentation: Provides clear guidelines for writing user-facing release notes that focus on API changes, breaking changes, and migrations.
Initial Release Protocol: Enforces the correct workflow for new packages, ensuring the first published version is 1.0.0 with a clean changelog.

Quick Start

Ask the agent to audit the current pull request to determine if a changeset is required based on the changeset-discipline guidelines.

Frequently Asked Questions about changeset-discipline

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

FAQPage Schema

How do I filter internal implementation details from automated changelogs?▼

Release notes should document API changes, breaking changes, and migrations. Apply strict criteria to filter internal hygiene changes, ensuring downstream users only see information relevant to their upgrade decisions.

When do I need to add a changeset entry during package development?▼

A changeset entry is required when code modifications introduce user-observable changes like API updates or breaking changes, while internal refactoring tasks that do not affect downstream users are ignored.

How do I manage versioning criteria for major, minor, and patch releases?▼

Enforce specific criteria for major, minor, and patch versioning during package development cycles to ensure automated changelog generation aligns with standardized version control workflows.

What is the correct workflow for publishing the initial version of a new package?▼

The initial release protocol enforces publishing the first version as 1.0.0 with a clean changelog, ensuring new packages launch with standardized user-facing documentation.

Can I audit a pull request to determine if a changeset is required?▼

Yes, you can audit a pull request by evaluating code modifications against changeset-discipline guidelines to determine if user-facing documentation is necessary for the release cycle.