Changelog Generator from Supplied Git History

Generate a changelog draft from Git history

Provide commit entries or raw Git log text to request a reader-friendly changelog. You can state a format preference, then review the generated descriptions against the history you supplied.

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use changelog-generate-strale to create a simple update note. Obtain the actual change history before calling the Tool. If the user gives a public GitHub link, use only the change history the connected Agent can access; do not pass the link itself as if it were the history. If the requested changes are unclear, ask what to include instead of silently choosing a time period or number of changes. If the link is private or inaccessible, ask the user to paste the history; do not ask them to run a command. If both a link and pasted history are provided, ask which source to use rather than merging them. Preserve any available messages, dates and authors. Use a style only when the user requests one; do not invent a default. Reuse Toolmu, or connect at https://toolmu.com/SKILL.md. Check current availability and price, stay within the user’s authorized budget, and report the actual draft. Compare it with the supplied history, flag unclear or unsupported entries, and do not invent releases, breaking-change conclusions or version numbers. Return a draft for review; do not publish it.

Task:
Write a simple update note from [public project link] or [change history I provide]. If it is unclear which changes I mean, ask me. Use only changes you can access, mark anything unclear, and let me review the draft before sharing it.

Paste into your connected AI's conversation.

Connection guide

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Strale

Generate a changelog draft from Git history

Provide commit entries or raw Git log text to request a reader-friendly changelog. You can state a format preference, then review the generated descriptions against the history you supplied.

You receive

Review the changelog draft actually returned for your supplied history. Your Agent can compare any change groupings and descriptions with the original commits, flag unclear entries and help you refine the draft.

Start with your task

Write a simple update note from [public project link] or [change history I provide]. If it is unclear which changes I mean, ask me. Use only changes you can access, mark anything unclear, and let me review the draft before sharing it.

What to know

Check the draft before sharing it. Generated wording does not prove that every released change or breaking change is included, and commit messages alone may omit the context needed to describe a change accurately.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Optional
Format preference`queryParams.format`	`string`	Optional	Optional format text. The supplier describes Keep a Changelog, semantic and bullet styles, but the native schema declares no enum, default or exact option-token mapping. State the requested style and inspect the actual draft.
Commit entries`queryParams.commits`	`array`	Optional	Optional array described as entries containing message, author and date. The schema has no item or member definitions, required entry keys, count limits or date rules. Preserve the supplied commit content and available context.
Raw Git log text`queryParams.raw_log`	`string`	Optional	Optional text for a raw Git log. The native input is a string with no documented parser syntax, length limit or default. Provide the log content to be summarized and keep relevant messages and metadata intact.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "properties": {
        "format": {
          "type": "string"
        },
        "commits": {
          "type": "array",
          "description": "Array of {message, author, date}"
        },
        "raw_log": {
          "type": "string"
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Strale’s capability description describes grouping Git changes by type and turning commit messages into human-readable descriptions. It lists Keep a Changelog, semantic and bullet styles as presentation options. Review the actual draft to see how your preference was applied.

Commit messages can omit the user impact or the reason for a change. Include useful context in the supplied history where available, and resolve unclear entries before turning the draft into public release notes.

Generate a changelog draft from Git history

Generate a changelog draft from Git history

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Share a public project link

Paste the change history if needed

Review the draft before sharing