agent coding skill risk: low

Git Changelog Generator

Generate structured changelogs from git history by examining commits, grouping by time periods, classifying changes with emojis, and producing concise user-facing descriptions.

External action: low

SKILL 1 file

SKILL.md

Download

---
name: wiki-changelog
description: "Generate structured changelogs from git history. Use when user asks /\"what changed recently/\", /\"generate a changelog/\", /\"summarize commits/\" or user wants to understand recent development activity."
---
# Wiki Changelog

Generate structured changelogs from git history.

## When to Use
- User asks "what changed recently", "generate a changelog", "summarize commits"
- User wants to understand recent development activity

## Procedure

1. Examine git log (commits, dates, authors, messages)
2. Group by time period: daily (last 7 days), weekly (older)
3. Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
4. Generate concise user-facing descriptions using project terminology

## Constraints

- Focus on user-facing changes
- Merge related commits into coherent descriptions
- Use project terminology from README
- Highlight breaking changes prominently with migration notes

### When to Use
This skill is applicable to execute the workflow or actions described in the overview.

REQUIRED CONTEXT

git log (commits, dates, authors, messages)

ROLES & RULES

Focus on user-facing changes
Merge related commits into coherent descriptions
Use project terminology from README
Highlight breaking changes prominently with migration notes

EXPECTED OUTPUT

Format

structured_report

Constraints

focus on user-facing changes
merge related commits
use project terminology
highlight breaking changes with migration notes

SUCCESS CRITERIA

Focus on user-facing changes
Merge related commits into coherent descriptions
Use project terminology from README
Highlight breaking changes prominently with migration notes

CAVEATS

Dependencies

git log (commits, dates, authors, messages)
README

Missing context

Method or tool for examining git log and README content
Explicit output format or template
Handling for empty commit history or no user-facing changes

Ambiguities

Duplicate 'When to Use' section appears at the end with conflicting meta text.
Does not specify desired output format or structure for the changelog.
'Use project terminology from README' without indicating how the README is accessed or provided.

QUALITY

OVERALL: 0.60
CLARITY: 0.65
SPECIFICITY: 0.55
REUSABILITY: 0.70
COMPLETENESS: 0.45

IMPROVEMENT SUGGESTIONS

Remove the duplicate 'When to Use' section and its meta sentence.
Add a dedicated 'Output Format' section with a markdown template or example.
Specify concrete commands or tool calls for retrieving git history and README.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.