changelog-fragment

name

changelog-fragment

description

Create a changie changelog fragment in `.changes/unreleased/` for this repository. Use this skill whenever you make a user-facing code change (a feature, fix, behavior change, removal, or security fix) and need to record it for the changelog, whenever the user asks to "add a changelog entry", "add a change fragment", "run just change", or mentions changie, and whenever you are preparing a PR — this repo's PR CI fails when a commit uses a conventional-commit type that needs an entry but no fragment is present. Reach for this skill even if the user only says "note this in the changelog" without naming changie or fragments.

Changelog fragments (changie)

This repository tracks unreleased changes as individual changie fragments under .changes/unreleased/. At release time changie merge rolls every fragment into CHANGELOG.md and deletes them. Your job here is to add one correct fragment per meaningful change so nothing is lost and the release notes read well.

The PR workflow (.github/workflows/pr.yml, changie-check) inspects commit types and comments "Missing Changelog Entry" when a feat:/fix:/etc. commit lands without a fragment. Adding the fragment as part of your change keeps CI green.

What a fragment looks like

A fragment is a small YAML file with exactly three keys:

kind: Added
body: Added `just ort-*` recipes that generate a reference CycloneDX