Name: wiki-changelog
Rating: 57.599999999999994 (1 reviews)
Author: administrakt0r

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.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wiki-changelog/SKILL.md

The canonical home for this skill is wiki-changelog in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a reasonable high-level framework for changelog generation but lacks the concrete, actionable details that would make it truly useful—no git commands, no output template, no example changelog. The duplicated 'When to Use' section and lack of executable guidance are the main weaknesses.

Suggestions

Add concrete git commands (e.g., `git log --since='7 days ago' --format='%h %s (%an, %ad)'`) to make the procedure executable rather than descriptive.

Include an example output showing the expected changelog format with the emoji categories, so Claude knows exactly what to produce.

Remove the duplicated 'When to Use' section at the bottom, which adds no value and contains only a vague placeholder sentence.

Add a brief example of how to 'merge related commits into coherent descriptions'—e.g., show 3 raw commits and the single changelog entry they become.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but has a duplicated 'When to Use' section (the second one is vague filler), and the 'When to Use' content already appears in the description/frontmatter. Some minor redundancy but not severely verbose.	3 / 5
Actionability	The procedure is high-level and descriptive rather than executable. There are no concrete git commands (e.g., `git log --format=...`), no example output format, and no template for the changelog structure. Claude is told to 'examine git log' and 'classify commits' but not shown how.	2 / 5
Workflow Clarity	Steps are listed in a logical sequence, but there are no validation checkpoints, no example of expected output, and no guidance on handling edge cases like merge commits or empty periods. The workflow is present but lacks specificity.	3 / 5
Progressive Disclosure	For a simple skill with no bundle files, the content is reasonably well-organized into clear sections (Procedure, Constraints). The duplicate 'When to Use' section is a minor organizational flaw. No external references are needed for this scope.	4 / 5
	Total	12 / 20 Passed

Description

86%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description with an excellent 'Use when' clause containing natural trigger phrases that users would actually say. Its main weakness is limited specificity about what the changelog generation actually entails (e.g., grouping, formatting, date ranges). Overall, it's a strong description that would perform well in skill selection.

Suggestions

Add more specific capabilities like 'groups commits by type (features, fixes, breaking changes)', 'supports date range filtering', or 'formats output as markdown' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (git history/changelogs) and one concrete action (generate structured changelogs), but doesn't elaborate on specific capabilities like grouping by type, filtering by date range, or formatting options.	3 / 5
Completeness	Clearly answers both 'what' (generate structured changelogs from git history) and 'when' (explicit 'Use when' clause with multiple concrete trigger phrases like 'what changed recently', 'generate a changelog', 'summarize commits').	5 / 5
Trigger Term Quality	Excellent coverage of natural trigger phrases: 'what changed recently', 'generate a changelog', 'summarize commits', 'recent development activity', 'git history'. These are exactly what users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on changelogs from git history, but could have minor overlap with a general git skill or a commit message skill. The specific trigger phrases help differentiate it, though 'summarize commits' could overlap with a git log viewing skill.	4 / 5
	Total	17 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wiki-changelog/SKILL.md
Commit: 0159794

Reviewed: ~8 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.