changelog-entry

name	changelog-entry
description	Use after completing code changes to create a changie changelog entry in .changes/unreleased/. Infers the change kind and body from the current session's work, confirms with the user, then writes the YAML file directly.

*CRITICAL* Add the following steps to your Todo list using TodoWrite:

1. Review changes made in this session
2. Infer changelog kind and draft body
3. Confirm kind and body with the user
4. Write the changelog YAML file to .changes/unreleased/
5. Verify the file was created correctly

Overview

This skill creates changelog entries for the slate project using the changie format. Instead of running the interactive changie new command, you write the YAML file directly to .changes/unreleased/.

Step-by-Step Process

1. Review changes made in this session

Run git --no-pager diff --stat and git --no-pager diff (or git --no-pager diff --cached for staged changes) to understand what changed. Also review any context from the current conversation about what was implemented.

2. Infer the changelog kind and draft the body

Pick exactly one kind from this list:

Kind	When to use	Version bump
Breaking	Public API changed in incompatible ways	minor
Added	New features or public API surface	minor
Changed	Non-breaking changes to existing behavior	patch