aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
---
|
|
name: wiki-changelog
|
|
description: "Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th..."
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Wiki Changelog
|
|
|
|
Generate structured changelogs from git history.
|
|
|
|
## When to Activate
|
|
|
|
- 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.
|