Wiki Changelog

SkillDocs & knowledge

Lets your agent read git history and turn recent commits into a clear, categorized changelog.

Then ask your AI: use the Wiki Changelog skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

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.

What this skill tells your AI

The instructions your AI receives, as published by microsoft/skills in .github/plugins/deep-wiki/skills/wiki-changelog/SKILL.md and read by Ahel’s review.

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)

Signals

GitHub stars: 3k
Forks: 350
Last commit: Oct 2026

Advanced

Item type: skill
Key: wiki-changelog
Source: github.com/microsoft/skills

github.com/microsoft/skills