Commit Release Notes

What it does

Group exported conventional commit subjects into draft release notes and flag declared breaking changes.

How to use it

Give the assistant the concrete task and required inputs. This fictional request illustrates the contract; use your selected files and parameters for real work.

{
  "version": "1.1.0",
  "commits": [
    {
      "id": "abc123",
      "subject": "feat!: change interface"
    },
    {
      "id": "def456",
      "subject": "fix: preserve settings"
    }
  ]
}

Output and verification

Creates a JSON report and, when applicable, CSV, Markdown or document artifacts in the current workspace. Inputs remain intact. Five offline tests cover the example, invalid input, actual CLI output, path boundaries and non-overwrite behavior. Live account, browser and visual results require separate verification.

Scope

This does not inspect code or validate that commit messages are accurate. Check the actual diff and test evidence; publishing a release remains separate. Preserve issue links and avoid claiming untested fixes.