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

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

Quality

Content

72%

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

The content is highly actionable with concrete commands and examples, and it is well-organized as a single-file skill. The main gap is that the actual changelog-generation workflow is described as capabilities rather than as an explicit, validated, multi-step procedure.

Suggestions

Reframe "What It Does" as a numbered, executable changelog-generation workflow (e.g., run `pnpm changeset`, then categorize commits, then draft entries in docs/changelog.md) rather than a capability list.

Add an explicit validation/verification checkpoint in the generation workflow, such as confirming each categorized entry maps to a real commit before finalizing.

Trim the redundant intro-vs-"What It Does" overlap and remove or fix the `../documentation/SKILL.md` reference so it resolves.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient (tables, bullets, no explanation of git/changesets concepts), but the intro paragraph overlaps the "What It Does" list and the "Related Skills" table references a path that does not resolve here, so it could be tightened.	2 / 3
Actionability	Provides the executable command `pnpm changeset`, concrete heading/emoji formatting rules, and a copy-paste-ready changelog example with before/after code blocks, matching the score-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	The changeset creation and bug-fix documentation sub-flows are sequenced and a checklist exists, but the core changelog-generation flow (scan, categorize, translate, format, filter) is presented as a capability list rather than an executable sequence with validation checkpoints; missing validation for batch operations caps clarity at 2.	2 / 3
Progressive Disclosure	A single self-contained file with well-organized sections and no deep/nested references; per the simple-skill scoring note, clear organization without a need for external references scores 3.	3 / 3
	Total	10 / 12 Passed

Description

60%

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 is specific and action-oriented but falls short on explicit trigger guidance, which caps both completeness and distinctiveness at 2. Adding a concrete "Use when..." clause with natural trigger terms would lift the description to a top-tier score.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when writing release notes, updating docs/changelog.md, or preparing a new version."

Broaden trigger terms to include user-phrased variants like "what changed", "version log", and "changelog entry".

Drop or de-emphasize the marketing line ("Turns hours of manual changelog writing into minutes...") since it adds tokens without aiding discovery.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes" — matching the score-3 anchor for listing several specific actions.	3 / 3
Completeness	Clearly states what the skill does but lacks a "Use when..." clause or equivalent explicit trigger guidance; the closing marketing line ("Turns hours...into minutes") does not serve as a trigger, so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains genuine natural terms ("changelogs", "git commits", "release notes") but misses common user variations like "what changed", "version log", or "changelog entry", fitting the score-2 anchor for partial keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The git-commit-to-changelog niche is somewhat distinct, yet the absence of explicit triggers and potential overlap with general documentation/release-note skills leaves it at the score-2 anchor for possible overlap with similar skills.	2 / 3
	Total	9 / 12 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: 8349acf

Reviewed: 2 days 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.