changelog-generator

Transform git commit history into polished user-facing changelogs and release notes. Use when the user wants a CHANGELOG.md from a version tag or date range, weekly product updates, app store release notes, or Keep a Changelog formatted output with internal noise filtered out.

Quality

81%

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

Quality

Content

78%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 a compact, well-structured instruction-only skill with concrete commit-prefix grouping rules and guardrails. Its main weakness is the lack of an executable example git command and an explicit validation/retry loop, though neither is strictly required for this low-risk read-and-generate task.

Suggestions

Add one concrete executable example, e.g. `git log v1.4.0..v1.5.0 --pretty=format:'%h %s'`, so the gather step is copy-paste ready rather than implied.

Include an explicit validation checkpoint (e.g. 'verify the commit range is non-empty and the repo root is correct before generating') to strengthen the workflow's feedback loop.

Trim the Example Prompts and Source Repository sections or move install info out of the core workflow to tighten token efficiency further.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanations of git or changelog concepts), though the grouping-rules table partially restates workflow step 3 and the Source Repository / Example Prompts sections add length that could be trimmed.	4 / 5
Actionability	Provides concrete, actionable guidance — specific commit prefixes (feat:, fix:, perf:, refactor:, security:, chore:, ci:, test:) mapped to categories, named output formats, and character-limit awareness — but never gives a concrete executable `git log` invocation with flags, leaving a minor gap.	4 / 5
Workflow Clarity	A clear six-step workflow (gather, filter, group, rewrite, format, output) supported by guardrail checkpoints (confirm ambiguous repo root, flag breaking changes, respect platform limits); the operation is low-risk/read-only so the destructive-batch cap does not apply, but explicit validate/retry feedback loops are absent.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no external references; no bundle files exist and none are needed, so the simple-skill structure earns the top mark for navigation and organization.	5 / 5
	Total	17 / 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 well-crafted description that clearly states the skill's purpose and provides an explicit, trigger-rich 'Use when' clause covering the main output formats. It is mostly specific and distinct, with only minor room to broaden action and synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Transform git commit history into polished user-facing changelogs and release notes', 'internal noise filtered out', plus multiple output formats (CHANGELOG.md, app store notes, Keep a Changelog) — but stops short of naming the gather/categorize processing steps, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (transform git history into changelogs/release notes with noise filtered) and 'when' via a concrete 'Use when the user wants a CHANGELOG.md from a version tag or date range, weekly product updates, app store release notes...' trigger clause.	5 / 5
Trigger Term Quality	Strong natural-term coverage including 'CHANGELOG.md', 'version tag', 'date range', 'weekly product updates', 'app store release notes', and 'Keep a Changelog', with good synonym variation, though a few common phrasings (e.g. 'release notes from commits', '.md') are not exhaustively present.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (user-facing changelog/release-note generation from git history) with distinct output-oriented triggers, with only minor overlap risk against generic commit-message or git-helper 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: eigent-ai/agent-skills
Path: skills/git-and-github/changelog-generator/SKILL.md
Commit: 9be8efc

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.