---
name: Changelog Generator
slug: changelog-generator
category: Writing
description: Changelog Generator creates customer-facing release notes from git commits and PR diffs. Use it after implementation or PR completion to group user-visible changes into features, fixes, and improvements.
github: "https://github.com/devton/agentic-workflow-blueprint/tree/main/workflows/changelog-generator"
stars: 66
forks: 4
install: "npx degit https://github.com/devton/agentic-workflow-blueprint/tree/main/workflows/changelog-generator ~/.claude/skills/changelog-generator"
installs_to: ~/.claude/skills/changelog-generator
source_path: workflows/changelog-generator/SKILL.md
collection_size: 26
category_size: 1012
collection_url: "https://dirskills.com/collections/devton/agentic-workflow-blueprint"
added: 2026-08-12T04:44:01.690Z
last_synced: 2026-08-12T04:44:01.690Z
canonical_url: "https://dirskills.com/skills/changelog-generator"
---

# Changelog Generator

Changelog Generator creates customer-facing release notes from git commits and PR diffs. Use it after implementation or PR completion to group user-visible changes into features, fixes, and improvements.

**Install:**

```bash
npx degit https://github.com/devton/agentic-workflow-blueprint/tree/main/workflows/changelog-generator ~/.claude/skills/changelog-generator
```

## README

## agentic-workflows-blueprint.workflow.changelog-generator

### Goal

Analyze session git commits and generate user-facing release notes categorized by features, fixes, and improvements.

### Scope

- **Applies to**: Post-implementation delivery and PR completion.
- **Does not cover**: Internal dev notes or technical refactor logs (keep those in code comments).

### Triggers

- "/changelog-generator"
- "Generate user changelog"
- "Summarize release notes"

### Inputs

- `baseBranch`: Target integration branch (`main`, `develop`).
- `commits`: Git commits in session.

### Invariants

1. **User Perspective**: Write for end users, not backend implementation details.
2. **Clear Categorization**: Group into Features, Fixes, and Improvements.

### Procedure

1. Run `git log` against `baseBranch` to inspect session commits.
2. Filter and categorize user-visible changes.
3. Transform technical language into clear benefit-driven descriptions.
4. Output changelog section into `walkthrough.md`.

### Outputs

- User-facing Changelog entry in `walkthrough.md`.

### Review gate

- Changelog reflects user-facing impact accurately.

### References

- `../../SKILL.md`
- `../radioactive/SKILL.md`
- `../changelog/SKILL.md`
- [Interactive HTML View](./README.html)