wiki-changelog
Analyzes git history to generate structured, user-facing changelogs grouped by change type.
Install
mkdir -p .claude/skills/wiki-changelog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1236" && unzip -o skill.zip -d .claude/skills/wiki-changelog && rm skill.zipInstalls to .claude/skills/wiki-changelog
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Analyze git commit history
- →Categorize changes by type
- →Generate structured release notes
- →Link commits and files to remote repository
- →Highlight breaking changes
How it works
It parses the git log, classifies commits into categories like features and fixes, and merges related changes into a readable format. It optionally links references to a remote repository.
Inputs & outputs
When to use wiki-changelog
- →Generate release notes for a version update
- →Summarize weekly development activity
- →Format commit history for stakeholders
About this skill
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 originto 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
- Remote URL provided → store as
- 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_URLis available, link commit hashes:[abc1234](REPO_URL/commit/abc1234)and changed files:[file_path](REPO_URL/blob/BRANCH/file_path)
When not to use it
- →For repositories without git history
- →When the user does not want a categorized changelog
Prerequisites
Limitations
- →Depends on commit message quality
- →Requires manual resolution of remote URL
How it compares
It automates the categorization and formatting of commit logs into a user-facing changelog, rather than providing a raw commit list.
Compared to similar skills
wiki-changelog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| wiki-changelog (this skill) | 3 | 4mo | No flags | Beginner |
| resume-builder | 53 | 3mo | No flags | Beginner |
| write-docs | 6 | 3mo | No flags | Beginner |
| changelog-generator | 3 | 10mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
resume-builder
amruthpillai
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
changelog-generator
ComposioHQ
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
docs-changelog
google-gemini
Provides a step-by-step procedure for generating Gemini CLI changelog files based on github release information.
docs-writer
google-gemini
Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.
document-writer
onmax
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.