GitHub Copilot ChatGPT Claude Codex CLI Cursor opencode Skill Text

wiki-changelog

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.

Ciza · 0 points · 25 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download microsoft-skills-.github_plugins_deep-wiki_skills_wiki-changelog-e58528d.zip · 1 KB

microsoft/skills 3052 351 forks MIT Updated 1d ago

Part of microsoft/skills — 195 skills

Install

skills CLI npx skills add https://github.com/microsoft/skills/tree/main/.github/plugins/deep-wiki/skills/wiki-changelog

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install microsoft-skills@llmmart

Git git clone https://github.com/microsoft/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole microsoft/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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:

Check for git remote: Run git remote get-url origin to detect if a remote exists
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
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

Examine git log (commits, dates, authors, messages)
Group by time period: daily (last 7 days), weekly (older)
Classify each commit: Features (🆕), Fixes (🐛), Refactoring (🔄), Docs (📝), Config (🔧), Dependencies (📦), Breaking (⚠️)
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)

Files (skills)

SKILL.md 1.8 KB

---
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)`