generate-changelog

generate-changelog is a command for Claude Code from ParkerM2/create-claude-workflow. It costs 16 tokens per session (2,978 once invoked), scanned A, original, MIT.

A command that creates a user-facing changelog from merged pull requests and Git commits between two Git references. A GitHub Release is a published version entry that can include these notes.

In plain words
What is it for?
Use it to generate Markdown or Keep a Changelog output, choose the source and target tags or references, append the result to a file, or publish it to a GitHub Release and Slack.
Why use it?
It turns technical commit history into organized release notes and classifies changes such as features, fixes, breaking changes, and dependency updates.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-workflow plugin — 10 skills, 25 commands, 3 agents, 6 hooks shipped together

Good fit Use it to generate Markdown or Keep a Changelog output, choose the…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/parkerm2/create-claude-workflow/generate-changelog
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/ParkerM2/create-claude-workflow

Made for: Claude Code.

Or install claude-workflow, the plugin that ships this one along with the rest of its 10 skills, 25 commands, 3 agents, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for generate-changelog

README.md
[![agentmods](https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/generate-changelog.svg)](https://agentmods.dev/commands/parkerm2/create-claude-workflow/generate-changelog)
Your own site
<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/generate-changelog"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/generate-changelog.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,978 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.02978
Opus 5 $0.00008 $0.01489
Sonnet 5 $0.00003 $0.00596
Haiku 4.5 $0.00002 $0.00298

Measured 6d ago against content hash bb07738652cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

generate-changelog scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const tags = execSync("git tag --sort=-version:refname --list 'v*' | head -20")
.claude/commands/generate-changelog.md · 406 lines

How it starts

The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automated Changelog Generation

Generates a production-ready changelog by aggregating merged PRs since the last release/tag. Auto-classifies entries by type (features, fixes, breaking changes, dependencies). Outputs markdown and optionally publishes to GitHub Release and Slack.

Usage

/generate-changelog [--from <tag>] [--to <ref>] [--github-release] [--slack] [--file <path>] [--format keep-a-changelog]
  • --from <tag>: Start from git tag (defaults to last tag)
  • --to <ref>: End at git ref (defaults to HEAD)
  • --github-release: Create GitHub Release with changelog
  • --slack: Post summary to Slack channel
  • --file <path>: Append changelog to file (CHANGELOG.md by default)
  • --format: Output format (keep-a-changelog, simple)

Workflow

Phase 1: Detect Version Range

Identifies commit range between last release and HEAD.

// Detect last git tag
let fromRef = null;
try {
  const tags = execSync("git tag --sort=-version:refname --list 'v*' | head -20")
    .toString()
    .trim()
    .split("\n")
    .filter(t => t);

  if (tags.length === 0) {
    fromRef = execSync("git rev-list --all | tail -1").toString().trim();
    console.log(`ℹ No tags found; scanning from first commit`);
  } else {
    fromRef = tags[0];
    console.log(`✓ Last release: ${fromRef}`);
  }
} catch (err) {
  console.error(`ERROR: Failed to detect git tags: ${err.message}`);
  return gracefulFailure("Unable to detect version range; specify --from manually");
}

const toRef = argv.to || "HEAD";

// Verify range is valid
try {
  const logOutput = execSync(`git log --oneline ${fromRef}..${toRef}`);
  const commitCount = logOutput.toString().split("\n").filter(l => l).length;
  console.log(`✓ Commit range: ${fromRef}..${toRef} (${commitCount} commits)`);
} catch (err) {
  console.error(`ERROR: Invalid git range ${fromRef}..${toRef}`);
  return gracefulFailure("Unable to determine changelog range");
}

Graceful degradation: If no tags, scan from first commit; allow manual range specification.

Read the full file on GitHub · 406 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 406 lines · 16 tokens per session scan A bb07738652cb

Subscribe to this mod's changes

generate-changelog is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 2,978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.