Changelog Writer

A skill that turns a pile of merged commits and pull requests into a clean, user-facing changelog entry — the kind you publish in release notes, not the raw git log developers read.

What it does

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

1. Parses your commits/PRs (Conventional Commits aware).
2. Drops noise — chores, CI, build, test, refactors with no behavior change, dependency bumps, and anything internal.
3. Deduplicates commits that belong to the same PR or feature.
4. Buckets the rest into Breaking Changes, Features, Improvements, Bug Fixes, and Documentation.
5. Rewrites each line as a user-benefit sentence (what changed for them, not the implementation), with a migration note on each breaking change.

What to feed it

A release version (optional) plus a list of merged commits or PRs. It accepts:

• JSON objects (subject/title, body, number, author, labels, hash)
• a Markdown bullet list
• raw git log output

Conventional Commits prefixes (feat, fix, perf, docs, chore, …) and !/BREAKING CHANGE: markers are used to classify and filter automatically. Optionally pass a target version and date.

What it returns

A Markdown changelog entry with a version/date heading and only the non-empty sections, each bullet a single user-facing sentence ending with an optional (#PR) reference. If nothing user-facing remains, it returns a single _No user-facing changes in this release._ line. Output is Markdown only — no preamble or commentary — so it drops straight into a CHANGELOG.md.