Wiki changelog
Skill Ghosteken/agent-harness/archive/skills-community/wiki-changelog
Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.From its SKILL.md
npx -y skills add Ghosteken/agent-harness --skill wiki-changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 201 tokens by cl100k_base, as published. Nobody here has run it
Wiki Changelog
Generate structured changelogs from git history.
When to Use
- 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 to Use
This skill is applicable to execute the workflow or actions described in the overview.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most readme changelog skills give in 201 tokens
Counted across 446 of the 460 authors here whose files we hold, read 2026-09-06
- Follow Keep a Changelog formatin 24 of 446
- Collect commits since the last git tagin 15 of 446, across 13 files
- Omit empty sectionsin 14 of 446
- Put breaking changes first with migration stepsin 14 of 446
- Include migration guidance for breaking changesin 11 of 446, across 10 files
- Categorize commits by conventional commit prefixin 11 of 446
- Mark breaking changes prominentlyin 10 of 446
- Prepend the new entry to CHANGELOG.mdin 9 of 446
- Highlight breaking changes with migration noteshere, and in 8 of 446, across 7 files
- Classify changes into Keep a Changelog categoriesin 8 of 446, across 7 files
- Group related commits into single entriesin 8 of 446
- Write the changelog from commitsin 8 of 446
Said here and by no other author read
- group commits daily for recent, weekly for older
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.