Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Git History Changelog Generator

agent coding skill risk: low

Git History Changelog Generator

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

  • External action: medium

SKILL 1 file

SKILL.md
---
name: antigravity-awesome-skills-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)

OPTIONAL CONTEXT

  • project README terminology

ROLES & RULES

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

EXPECTED OUTPUT

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

CAVEATS

Dependencies
  • git history
  • README
Missing context
  • How git history is accessed or provided as input
  • Target project README or terminology source
Ambiguities
  • Duplicate 'When to Use' section at the end that references an undefined 'overview'
  • Does not specify desired output format or structure

QUALITY

OVERALL
0.70
CLARITY
0.72
SPECIFICITY
0.78
REUSABILITY
0.68
COMPLETENESS
0.62

IMPROVEMENT SUGGESTIONS

  • Remove the redundant final 'When to Use' section
  • Add an explicit 'Output Format' section with a markdown template example

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.

MORE FOR AGENT