changelog-automation

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

Quality

61%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/changelog-automation/SKILL.md

Quality

Content

22%

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

This skill is essentially a thin table of contents pointing to an implementation playbook, with no actionable content in the main body. The instructions are entirely abstract directives that don't leverage Claude's capabilities or provide any concrete guidance on changelog automation tools, commit conventions, or configuration. The skill fails to deliver standalone value and relies entirely on referenced files that aren't provided.

Suggestions

Add concrete, executable examples directly in SKILL.md — e.g., a conventional commit format specification, a sample `.releaserc` or `cliff.toml` config, or a specific tool command like `git-cliff --config cliff.toml -o CHANGELOG.md`

Replace vague instructions ('Select a changelog format', 'Configure tooling') with specific steps naming actual tools (conventional-changelog, git-cliff, release-please) and their setup commands

Add a validation step with a concrete mechanism, e.g., 'Run `commitlint --from HEAD~5` to verify recent commits follow conventions before generating changelog'

Include at least one complete input/output example showing a set of commits and the resulting changelog entry in Keep a Changelog format

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate value but are somewhat verbose for what they convey. The instructions section is lean but vague. The 'Knowledge Modules (Fractal Skills)' header with emoji is unnecessary padding.	2 / 3
Actionability	The instructions are entirely abstract ('Select a changelog format', 'Enforce commit conventions', 'Configure tooling') with no concrete code, commands, tool names, or executable examples. There is nothing copy-paste ready or specific enough for Claude to act on without the referenced playbook.	1 / 3
Workflow Clarity	The steps are vague directives without specific sequencing, validation checkpoints, or feedback loops. 'Review output for accuracy' is the only hint of validation, but it lacks any concrete mechanism. For a workflow involving automated release processes, this is insufficient.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` and a sub-skill, which is appropriate progressive disclosure structure. However, no bundle files are provided to verify these references exist, the references appear in multiple places redundantly, and the main skill provides almost no standalone value without the referenced files.	2 / 3
	Total	6 / 12 Passed

Description

100%

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 strong skill description that clearly communicates its purpose, uses natural trigger terms, and explicitly states both what it does and when to use it. It follows the recommended pattern with concrete actions, a specific format standard, and an explicit 'Use when' clause. The description is concise yet comprehensive, making it easy for Claude to select appropriately.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'changelog generation from commits, PRs, and releases', 'setting up release workflows', 'generating release notes', 'standardizing commit conventions'. Also references a specific format standard (Keep a Changelog).	3 / 3
Completeness	Clearly answers both what ('Automate changelog generation from commits, PRs, and releases following Keep a Changelog format') and when ('Use when setting up release workflows, generating release notes, or standardizing commit conventions') with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'changelog', 'commits', 'PRs', 'releases', 'release notes', 'release workflows', 'commit conventions', 'Keep a Changelog'. These cover common variations of how users would describe this need.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche around changelog generation and release note automation. The specific mention of Keep a Changelog format, commit conventions, and release workflows makes it unlikely to conflict with general git or documentation skills.	3 / 3
	Total	12 / 12 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: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

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