Changelog Generator

Write a user-facing changelog from git commits, grouped by type, in Keep a Changelog, semantic or bullet format.

Pay by wallet (x402) AI-generated changelog-generate

Example

Example answer
{
  "format": "",
  "sections": [],
  "commit_count": 0,
  "breaking_changes": [],
  "changelog_markdown": "## [Unreleased]\n\nNo changes yet.",
  "version_suggestion": "patch"
}

Inputs

FieldTypeRequiredWhat it is
formatstringNo—
commitsarrayNoArray of {message, author, date}
raw_logstringNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
sectionsarrayAlways (present in every successful answer)
breaking_changesarrayAlways (present in every successful answer)
changelog_markdownstringAlways (present in every successful answer)
version_suggestionstringAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "changelog-generate",
    "inputs": {
      "commits": [
        {
          "message": "Add user authentication"
        },
        {
          "message": "Fix login validation bug"
        },
        {
          "message": "Update dependencies"
        }
      ]
    },
    "max_price_cents": 3
  }'

Limitations

  • User-facing changes can be misidentified

    AI-generated changelog from commit messages or diffs — may not correctly identify user-facing impact vs internal changes

    What to do instead: Use conventional commit prefixes (feat:, fix:, chore:) in your commits for more accurate categorisation