# Release Notes

> Use this skill when asked to write versioned release notes and you need repo-specific structure, ordering, and scope filtering.

- Skill: `dekart-xyz/release-notes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dekart-xyz/release-notes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dekart-xyz/release-notes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dekart-xyz (https://skillmd.com/u/dekart-xyz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dekart-xyz/release-notes

---


# Release Notes Skill

## Trigger

Use this skill when asked to write release notes.

## Instructions

- Use `docs/release-notes-0-21-0.md` as the formatting template and section style baseline.
- Present items in this exact order:
  1. User-facing features first.
  2. Operator behavior changes second.
  3. Other changes important for admins/operators third.
  4. User-facing bug fixes fourth.
  5. Upgrade instructions last.
- Add a dedicated `Behavior Changes` section for changes that can alter existing deployment behavior or require operator action.
- Include environment variables only when they are relevant to operator action, compatibility, or upgrade safety. Do not include exhaustive variable inventories.
- Skip chore/internal-only changes that do not affect users or admins (for example CI/workflow-only changes).
- Keep language outcome-focused (what changed for users/admins), not implementation-heavy.
- Include only changes in the requested version/tag diff range.
- Use the major.minor release version in release-note copy and image tags (for example `0.23`).
- Never mention release-candidate tags or patch versions in release notes, even when an RC commit or tag defines the diff endpoint.
- Every `DEKART_LICENSE_KEY` mention must include the CTA: `[Get a key free here](https://mailchi.mp/dekart/upgrade-to-sso)`.