What does this skill do, and when should you use it?
Wiki Changelog is for users who need a clear view of recent repository activity. It reads Git commit history, including commit dates, authors, and messages, then organizes the results by time period and change type. Before producing a changelog, it resolves whether the repository is local-only or associated with a source URL. When a repository URL is available, it can link commit hashes and changed files.
Runs git remote get-url origin to check for a remote; asks whether the repository is local-only or has a source repository URL; after the repository context is resolved, examines Git commits, dates, authors, and messages; groups commits daily for the last seven days and weekly for older periods; classifies commits as Features, Fixes, Refactoring, Docs, Config, Dependencies, or Breaking; merges related commits into concise user-facing descriptions; and adds linked commit hashes and file references when REPO_URL is available.
- A maintainer needs a concise changelog for the past week of repository activity.
- A development team wants commits grouped into features, fixes, refactoring, and other change categories.
- A new contributor wants to understand recent project development through commit history.
- A project owner needs breaking changes highlighted with migration notes.
How do you install this skill?
- The skill depends on local git history and possibly remote repository access, but does not define clear fallback behavior or error messages for unavailable git, unreachable remotes, or empty repositories.
- No structured output schema or example is provided, so consistency and direct usability require human review.
- Chinese terminology, Chinese templates, and mainland-China network reachability are not documented.
- Shell / CLI
- Local filesystem
Git
In Copilot CLI, run: /plugin marketplace add microsoft/skills, then run: /plugin install deep-wiki@skills. The skill is located at .github/plugins/deep-wiki/skills/wiki-changelog/SKILL.md. Alternatively, run npx skills add microsoft/skills and select the required skills in the installer; the source does not document how to select this specific plugin skill through that wizard.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/microsoft/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/.github/plugins/deep-wiki/skills/wiki-changelog" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- What changed recently?
- Generate a changelog,
- Summarize the commits.
- Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?
Trigger it with requests such as “What changed recently?”, “Generate a changelog,” or “Summarize the commits.” Before generating output, it runs git remote get-url origin and asks: “Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?” It does not continue until the repository context is resolved.
What are this skill's strengths and limitations?
- Defines a concrete workflow for reading commits, grouping time periods, classifying changes, and writing user-facing summaries.
- Highlights breaking changes and requires migration notes.
- Supports linked commit hashes and changed-file references when a source repository URL is provided.
- Released under the MIT license and maintained within an actively developed Microsoft Agent Skills repository.
- The source-repository context must be resolved before changelog generation can proceed.
- The source does not provide independent test coverage or a platform matrix for this individual skill.
- Results depend on the availability and quality of Git commit metadata and messages.
- It summarizes Git history but does not review code or modify the repository.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Wiki Changelog Assistant this page ✓ Microsoft · Official | 51 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Commit Assistant ✓ Microsoft · Official | 56 · Use with care | ★ 194k | 11d ago | MIT |
| Changelog Scan Skill | 45 · Not recommended | ★ 12k | 11d ago | MIT |
| Changelog Scanner | 43 · Not recommended | ★ 12k | 11d ago | MIT |
| Release Notes Drafting Skill | 32 · Not recommended | ★ 12k | 11d ago | MIT |
How did FollowSkills review this skill?
The skill requires checking git remote first and asking the user to resolve local versus remote repository context before proceeding; it also specifies linked citations for remote sources, supporting scope control and source transparency. It does not address sensitive-data handling, detailed permission boundaries, rollback, or external-network failure handling, so full marks are not justified.
The procedure is internally understandable and covers log inspection, classification, and user-facing summarization. However, the meaning of “recent,” behavior when git or the repository is unavailable, diagnostic failure feedback, and how BRANCH is selected for links are unspecified. Static review provides no skill-specific execution evidence, so the score remains below the static ceiling.
Activation phrases and the main use case are clear for commit-history and change-summary requests. Inputs, output structure, non-fit cases, abnormal-repository boundaries, Chinese-language support, and mainland-China network fit are not defined, so adaptability is only partial.
The SKILL.md includes name, description, MIT license, author, and version metadata, and uses a readable structure covering resolution, activation, procedure, and constraints. It lacks examples, FAQs, known limitations, changelog, explicit maintenance responsibility, and an update path. Repository README and CI provide only repository-level context, not skill-specific governance.
The core procedure can plausibly produce a time-grouped, categorized, user-facing changelog and calls for highlighting breaking changes. There is no fixed output schema, representative example, or verification result, and link construction may require manual completion, so only partial core effectiveness is supported.
The skill contains auditable procedural claims, and the repository shows generic tests and CI. The supplied tests do not cover wiki-changelog key paths, and no real execution result or independent corroboration is provided, leaving evidence coverage thin.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →