microsoft / wiki-changelog
Install for your project team
Run this command in your project directory to install the skill for your entire team:
mkdir -p .claude/skills/wiki-changelog && curl -L -o skill.zip "https://fastmcp.me/Skills/Download/1236" && unzip -o skill.zip -d .claude/skills/wiki-changelog && rm skill.zipProject Skills
This skill will be saved in .claude/skills/wiki-changelog/ and checked into git. All team members will have access to it automatically.
Important: Please verify the skill by reviewing its instructions before using it.
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.
0 views
0 installs
Skill Content
--- 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. --- # 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)`