// Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.
Use when creating or updating skills, testing skill behavior with subagents, repairing unclear triggers or observed misbehavior, designing pressure tests, closing loopholes, addressing rationalizations, or validating skill folders before deployment.
Mandatory for Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, pull request updates, review submission, publishing, or recovery from raw Git usage. Use git-spice for supported operations; do not bypass git-spice for commits, branches, stack movement, pushes, or pull request submission.
Use when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Load and follow the git-spice skill for the workflow.
Use when creating pull requests, updating pull request branches, pushing or publishing work for review, editing pull request metadata, or submitting stacked branches. Load and follow the git-spice skill for the workflow.
| name | changie |
| description | Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`. |
Use this skill only if the repository has a .changie.yaml file.
If .changie.yaml is absent,
this skill does not apply.
This skill covers how to use changie directly,
choose the correct kind from .changie.yaml,
and write changelog body text.
Add a changelog entry when the change is user-facing. Typical examples include:
Do not add a changelog entry for work that has no user-facing effect. Typical examples include:
Use changie directly by default:
changie new --kind $kind --body $body
Prefer generating the entry through Changie instead of hand-writing the file. That preserves the expected filename, timestamp, and directory layout.
Read the allowed kinds from .changie.yaml.
Common kinds include:
AddedChangedDeprecatedRemovedFixedSecurityChoose the kind based on the user-visible outcome, not the implementation detail.
Examples:
Added.Changed.Fixed.Deprecated.Removed.If .changie.yaml defines custom kinds,
use those instead of generic assumptions.
The body should describe the user-facing effect.
.changie.yaml.Good bodies usually answer: "What changed for the user?"
Weak bodies usually describe only internal work, for example:
refactor API clientcleanupmove code into helperThose are engineering notes, not release notes.
If changie is not found,
look for repository-specific wrappers before doing anything else.
Check:
mise.tomlMakefileIf either file defines a wrapper for running changie,
use that wrapper instead of assuming a global changie binary exists.