changelog

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.

Quality

70%

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 ./.agents/skills/changelog/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The body is well-structured and actionable with concrete commands, format specs, and examples, and a checklist for verification. It is held back from top marks by minor over-explanation, a couple of gaps in executable detail, and the absence of reference files to offload deeper content.

Suggestions

Tighten the 'What It Does' section and intro paragraph since they restate the description, to improve token efficiency.

Add a complete example of a changeset file's contents so the changeset workflow is fully copy-paste ready.

Consider moving the detailed changelog examples and category tables into a reference file referenced one level deep from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean tables, commands, and examples without explaining concepts Claude already knows; the 'What It Does' section and intro paragraph partially restate the description, giving minor over-explanation that keeps it at anchor 4 rather than 5.	4 / 5
Actionability	Concrete executable guidance is present (`pnpm changeset`, heading-level format spec, before/after code examples); minor gaps such as the lack of a full changeset file-format example keep it at anchor 4 rather than fully copy-paste-ready 5.	4 / 5
Workflow Clarity	Sub-workflows (changeset creation, bug-fix documenting) are clearly sequenced and a final Checklist provides a verification checkpoint; minor validation gaps and a somewhat fragmented end-to-end flow keep it at anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist, but the single-file body is well-organized with clear section headers and one-level-deep references (Related Skills table, external doc URLs); content that could be split (detailed examples) is inline, matching anchor 4 rather than the well-split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%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.

The description clearly states what the skill does with several concrete actions and good natural trigger terms, but omits any explicit 'Use when...' guidance, which caps its completeness. It is reasonably distinctive within its niche.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when preparing release notes, writing changelogs, or generating version notes from git history.'

Add a couple of natural synonyms ('what's new', 'version notes') to broaden trigger-term coverage.

Consider naming the formatting/filtering actions in the description to round out the capability coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes'), matching the 'several specific actions; minor gaps' anchor; the body covers formatting/filtering not named here, so it is not a 5.	4 / 5
Completeness	The 'what' is explicit but there is no 'Use when...' clause or equivalent trigger guidance; per the judging guideline a missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'changelogs', 'git commits', 'commit history', and 'release notes' give good keyword coverage with only a few synonyms missing (e.g., 'what's new', 'version notes'), matching anchor 4 rather than comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The niche of generating user-facing changelogs from git commits is mostly distinct, with only minor overlap risk against commit-message-writing skills, matching anchor 4.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: kubb-labs/kubb
Path: .agents/skills/changelog/SKILL.md
Commit: 1bbf973

Reviewed: about 18 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.