generate-changelog

Auto-generate project changelog

23 stars

Best use case

generate-changelog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Auto-generate project changelog

Teams using generate-changelog should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/generate-changelog/SKILL.md --create-dirs "https://raw.githubusercontent.com/wangjianjq/Skill/main/.agents/skills/generate-changelog/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/generate-changelog/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How generate-changelog Compares

Feature / Agent	generate-changelog	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Auto-generate project changelog

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Generate Changelog

Automatically generate changelog based on Git commit history.

## When to Use

- Before releasing a new version
- When summarizing project changes
- Generating release notes

## Execution Steps

1. Get recent Git commits
2. Group by type (features, fixes, refactors, etc.)
3. Generate formatted changelog

## Command

```bash
git log --oneline --pretty=format:"%h - %s (%an, %ar)" --since="30 days ago"
```

## Expected Result

Generates a changelog containing all commits from the last 30 days, sorted in reverse chronological order.