wiki-changelog — Claude Code skill: changelogs and setup
Turns Git commit history into a categorized changelog. Use it to review recent repository activity or explain what changed across a project.
npx skills add microsoft/skills --skill wiki-changelog -a claude-codeWhat wiki-changelog does
wiki-changelog reads commit dates, authors, messages, and other details from Git history. It sorts the last 7 days by day and older commits by week, then assigns entries to feature, fix, refactoring, documentation, configuration, dependency, or breaking-change groups.
The skill checks git remote get-url origin before it writes a changelog and asks whether the project is local-only or tied to a source repository. With a repository URL, commit hashes and changed files can point to linked references; otherwise the output keeps plain hashes and paths. Its summaries focus on changes visible to users, follow terminology from the README, and call out migration notes for breaking changes. It runs in Claude Code and GitHub Copilot.
What it helps with
- build a changelog from Git history
- sort recent commits by change type
- group repository activity by day and week
- flag breaking changes with migration notes
Example prompts for the agent
- Create a changelog from the recent repository history.
- Summarize what changed in the last 7 days of Git commits.
- Group the commits by type and highlight breaking changes.
How to install wiki-changelog
1Skills CLI (Vercel)
npx skills add microsoft/skills --skill wiki-changelog -a claude-code2Manually: put the files in place
~/.claude/skills/wiki-changelog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wiki-changelog/
Manually: put the files in place
.agents/skills/wiki-changelog/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/wiki-changelog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/skills wiki-changelog2Manually: put the files in place
.github/skills/wiki-changelog/SKILL.mdPlatform CLI
gemini skills install https://github.com/microsoft/skills --path .github/plugins/deep-wiki/skills/wiki-changelogManually: put the files in place
.devin/skills/wiki-changelog/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about wiki-changelog
How do I install wiki-changelog in Claude Code?
Run npx skills add microsoft/skills --skill wiki-changelog -a claude-code, then check ~/.claude/skills/wiki-changelog/SKILL.md.
What does wiki-changelog do?
It reads Git history, organizes commits by time period and change type, and produces a user-facing changelog with breaking changes called out.
Why does wiki-changelog ask for a source repository URL?
A repository URL lets the generated changelog link commit hashes and changed files. A local-only project uses plain hashes and paths, but the repository context must be resolved first.
Source text
SKILL.md · MIT
--- 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 the repository. license: MIT metadata: author: Microsoft version: "1.0.0" --- # Wiki Changelog Generate structured changelogs from git history. ## Source Repository Resolution (MUST DO FIRST) Before generating any changelog, you MUST determine the source repository context: 1. **Check for git remote**: Run `git remote get-url origin` to detect if a remote exists 2. **Ask the user**: _"Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"_ - Remote URL provided → store as `REPO_URL`, use **linked citations** for commit hashes and file references - Local-only → use plain commit hashes and file references 3. **Do NOT proceed** until source repo context is resolved ## 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 `REPO_URL` is available, link commit hashes: `[abc1234](REPO_URL/commit/abc1234)` and changed files: `[file_path](REPO_URL/blob/BRANCH/file_path)`
© Microsoft · MIT · microsoft/skills