agent coding skill risk: low

Git History Structured Changelog Generator

Generate structured changelogs from git history by examining commits, grouping by time period, classifying each commit, and producing concise user-facing descriptions.

SKILL 1 file

SKILL.md

Download

---
name: antigravity-awesome-skills-wiki-changelog-1f6fdbf9
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

markdown

Constraints

Focus on user-facing changes
Merge related commits into coherent descriptions
Use project terminology from README
Highlight breaking changes prominently 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

FAILURE MODES

May include internal or non-user-facing commits
May fail to merge related commits
May omit migration notes for breaking changes

CAVEATS

Dependencies

git log
README

Missing context

How to access or execute git log (command, tool, or environment).
Project README content or source for terminology.
Prerequisites such as presence of a git repository.

Ambiguities

Duplicate 'When to Use' section at the end creates redundancy.
Does not specify exact output format or structure.

QUALITY

OVERALL: 0.71
CLARITY: 0.72
SPECIFICITY: 0.78
REUSABILITY: 0.75
COMPLETENESS: 0.62

IMPROVEMENT SUGGESTIONS

Remove the redundant final 'When to Use' section.
Add an explicit 'Output Format' section with a markdown template or example.
Clarify prerequisites and how git history will be provided or accessed.

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.