Release Notes Drafter

Turns a raw list of changes — git commit subjects, PR titles, or plain bullets — into clean, user-facing release notes grouped under Added / Changed / Fixed, with breaking changes called out and a one-line headline summary.

What it does

The InTouch AI assistant loads this skill as a prompt and:

Filters out noise (CI/build/dependency bumps, internal-only refactors, test/formatting-only changes).
Classifies each remaining change into Added, Changed, or Fixed — using conventional-commit prefixes (feat:, fix:, refactor:, perf:…) when present, and wording cues when not.
Rewrites every line as a past-tense, user-facing sentence (strips prefixes, ticket/PR numbers, and internal module names).
Surfaces anything marked BREAKING CHANGE: / "removed" into a ⚠ Breaking Changes callout at the top.
Orders entries most-impactful first, drops empty groups, and appends a one-sentence changelog headline.

What to feed it

changes (required) — the change list, one per line. Commit subjects, PR titles, or freeform bullets all work; prefixes are optional.
version (optional) — release version string, e.g. 2.4.0. Defaults to Unreleased.
date (optional) — release date, e.g. 2026-06-13. Omitted from the heading if not supplied.

Example:

feat: add CSV export to the reports page
fix: dashboard crashed when a project had no jobs
refactor: rename "Owner" column to "Responsible"
perf: schedules list loads 3x faster
BREAKING CHANGE: removed the legacy /v1 API

What it returns

A Markdown release-notes block:

## 2.4.0 — 2026-06-13

### ⚠ Breaking Changes
- Removed the legacy /v1 API

### Added
- Added CSV export to the reports page

### Changed
- Schedules list now loads about 3x faster
- Renamed the "Owner" column to "Responsible"

### Fixed
- Fixed a crash on the dashboard for projects with no jobs

followed by a one-sentence headline summary of the release. If the input has no user-facing changes, it returns a short "No user-facing changes in this release." note instead.