Wiki changelog

Skill ComeOnOliver/skillshub/skills/microsoft/skills/wiki-changelog

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.From the repository description

Install

npx -y skills add ComeOnOliver/skillshub --skill wiki-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.5 KB, 362 tokens by cl100k_base, as published. Nobody here has run it

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)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.