Wiki Changelog

by microsoft354361d83247MITListed Oct 8, 2026Updated Oct 8, 2026

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.

FeaturedInstructions onlySoftware Development

AI-generated overview

Generates structured, categorized changelogs from a repository's git commit history.

What it does: This skill analyzes git log data — commits, dates, authors and messages — and produces a structured changelog. It groups changes by time period (daily for the last 7 days, weekly for older entries) and classifies each commit into categories such as features, fixes, refactoring, docs, config, dependencies and breaking changes. It writes concise user-facing descriptions using project terminology and highlights breaking changes with migration notes. When a source repository URL is available, it links commit hashes and changed files.
When to use it: Use it when a user asks what changed recently, requests a changelog, or wants to understand recent development activity in a repository. It first resolves whether the repository is local-only or has a remote URL before generating output.
Requirements: Instructions only; no scripts are shipped. It needs access to a git repository and the ability to run git commands such as git log and git remote get-url origin. A source repository URL (for example GitHub or Azure DevOps) is optional and only enables linked citations.

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)

Source and attribution

Source:microsoft/skillsin.github/plugins/deep-wiki/skills/wiki-changelogat commit354361d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Wiki Changelog

Wiki Changelog

Source Repository Resolution (MUST DO FIRST)

When to Activate

Procedure

Constraints

Source and attribution

More from microsoft/skills

Customize

Discover Azure Skills

Azure Resource Visualizer

Azure Resource Lookup

Azure Messaging

Azure Kusto

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Dpop Adoption

Gemini Live Api

Gemini Api