| name | add-changelog-entry |
| description | Create trellis changelog fragments for the lattice monorepo. Use this skill whenever the user mentions changelogs, changelog entries, changelog fragments, trellis changelog, "add a changelog", "add a change entry", or wants to document changes for a release. Also use proactively after completing user-facing code changes to any package, even if the user doesn't explicitly ask for a changelog entry. |
Changelog Entry Skill
This monorepo uses trellis's native changelog engine. Each entry is a TOML
fragment in .changes/unreleased/ that targets a specific package. Create
fragments with the CLI — it validates the package and kind and picks a free
filename:
trellis changelog new --package <pkg> --kind <kind> --body "<text>"
When to create entries
Create one entry per user-facing change per affected package. A single PR
might need multiple entries if it touches multiple packages or introduces
both a new feature and a breaking change in the same package.
Determining the right package and kind
Packages
Identify which package(s) the change affects by looking at which source files
were modified: a change under packages/<name>/ belongs to package <name>.
Run trellis list --releasable for the authoritative list of packages that
take changelog entries (examples/ does not).
If the change only affects tests, CI, docs, or internal tooling with no
user-facing impact, a changelog entry is probably not needed. Ask the user if
unsure.
Kinds
Kinds and their bumps are configured under [tools.trellis.changelog] in the
root gleam.toml. Pick the kind that best describes the change's impact on
users of that package:
