generate-changelog

Generate changelog entries from git commits, plan files, or structured data. Use for version releases, creating CHANGELOG.md sections, or documenting changes between versions.

Quality

77%

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

Quality

Content

71%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 an efficient, well-sequenced, instruction-style skill with concrete mapping rules and worked examples covering all three sources plus the empty case. Its main defect is the dangling commit-mapping.json reference (the file is absent from the bundle), and secondarily the missing explicit git log command for parsing commits.

Suggestions

Either create references/commit-mapping.json with the conventional-commit-to-category mapping and trim the inline Step 3 rules to point at it, or remove the Supporting Files section entirely — the current reference points to a file that does not exist.

Add the concrete git command for the git source, e.g. `git log v0.7.0..HEAD --pretty=format:"%s"`, so the parsing step is executable rather than implied.

Drop the redundant Step 5 "Expected Output" block, which near-duplicates Example 2's output, and keep one canonical output example.

Dimension	Reasoning	Score
Conciseness	The body is lean — terse step definitions, category mapping tables, and input/output examples with no explanation of concepts Claude already knows. It falls short of the every-token-earns-its-place anchor because Step 5's "Expected Output" example near-duplicates Example 2's output, and the four worked examples carry some redundancy.	4 / 5
Actionability	Input schemas, category mapping rules ("feat → Added", "chore → Omit"), output format templates, and four concrete input/output examples give mostly executable guidance. It is not fully copy-paste ready because git parsing says only "Parse git log between two refs" without the actual git command or pretty-format to use.	4 / 5
Workflow Clarity	Five clearly sequenced steps plus an Error Handling section and a Validation checklist give most needed checkpoints, matching the clear-sequence/minor-validation-gaps anchor. It is not a 5 because recovery guidance (e.g., what to do after an invalid git range) is listed as outcomes rather than embedded as validate-and-retry loops in the workflow.	4 / 5
Progressive Disclosure	Sections are well organized, but the single external reference — "`commit-mapping.json`: Conventional commit to changelog category mapping" under Supporting Files — points to a file that does not exist in the bundle (no references/, scripts/, or assets/ directories), and the mapping it promises is duplicated inline in Step 3. This is a dangling reference with inlined content that should live in the referenced file, fitting the some-structure/could-be-better-organized anchor.	3 / 5
	Total	15 / 20 Passed

Description

83%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.

A strong description: it answers what it does and when to use it with concrete, natural trigger phrases in third person, and it occupies a distinct niche. Minor gains available from adding "release notes" as a trigger synonym and tightening the breadth of "documenting changes between versions".

Dimension	Reasoning	Score
Specificity	"Generate changelog entries from git commits, plan files, or structured data" names the domain and concrete actions across three input sources, matching the 'several specific actions; minor gaps' anchor. It stays below the comprehensive-coverage anchor because the core action is a single one (generate entries) rather than multiple distinct operations.	4 / 5
Completeness	The 'what' is explicit ("Generate changelog entries from git commits, plan files, or structured data") and the 'when' is explicit with concrete triggers ("Use for version releases, creating CHANGELOG.md sections, or documenting changes between versions"), matching the top anchor. It is not a 4 because both halves are present and equally concrete.	5 / 5
Trigger Term Quality	"version releases", "CHANGELOG.md", "documenting changes between versions", "git commits", and "changelog" are natural user phrasings with good coverage. It misses a few common variations such as "release notes" or "what's changed", so it fits the good-coverage-with-gaps anchor rather than the comprehensive synonym/extension anchor.	4 / 5
Distinctiveness Conflict Risk	The changelog-generation niche is well delimited by CHANGELOG.md and version-release triggers, with only minor overlap risk with commit-message generation skills. It is not a 5 because "documenting changes between versions" is broad enough to brush against general documentation skills.	4 / 5
	Total	17 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: maslennikov-ig/claude-code-orchestrator-kit
Path: .claude/skills/generate-changelog/SKILL.md
Commit: 8c3b576

Reviewed: 6 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.