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.

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

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

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 (unavailable local link target: REPO_URL/commit/abc1234) and changed files: file_path (unavailable local link target: REPO_URL/blob/BRANCH/file_path)

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"}

Generate structured changelogs from git history.

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

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

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 (unavailable local link target: REPO_URL/commit/abc1234) and changed files: file_path (unavailable local link target: REPO_URL/blob/BRANCH/file_path)

wiki-changelog