wiki-changelog
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.
Click Get this skill. Grab the .md file, one click, no account needed.
Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.
Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.
Generate conventional commit messages by analyzing staged changes
Find and delete merged/stale local and remote branches
Safely undo the last git operation (commit, merge, rebase, etc.)
Generate CHANGELOG.md from git history using conventional commits
Analyze and suggest resolutions for merge conflicts
Automate git bisect to find the commit that introduced a bug
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.