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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-oss-maintainer/skills/changelog-automation/SKILL.md

Quality

Content

22%Scale 1-3

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 table of contents with no actionable content. It lacks any concrete code, commands, tool names, commit format examples, or changelog templates—all the substance is deferred to a referenced file that doesn't exist in the bundle. The instructions read as abstract project management guidance rather than executable steps Claude can follow.

Suggestions

Add concrete, executable examples: show a conventional commit format (e.g., `feat(auth): add JWT support`), a sample changelog entry in Keep a Changelog format, and at least one tool command (e.g., `npx conventional-changelog -p angular -i CHANGELOG.md -s`).

Replace the vague instruction bullets with a specific numbered workflow including validation steps, e.g., '1. Run `git log --oneline v1.0.0..HEAD` to gather commits, 2. Categorize by prefix, 3. Generate changelog, 4. Review for accuracy before committing.'

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns and templates directly in the SKILL.md so the skill is self-contained enough to be useful.

Remove the generic 'Limitations' boilerplate section—it adds no skill-specific value and wastes tokens.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate bloat—Claude doesn't need five bullet points explaining when to use a changelog skill. The 'Limitations' section is boilerplate that doesn't add skill-specific value. However, the overall length is reasonable.	2 / 3
Actionability	The instructions are entirely abstract ('Select a changelog format', 'Enforce commit conventions', 'Configure tooling') with zero concrete code, commands, tool names, or examples. There is nothing executable or copy-paste ready—it describes rather than instructs.	1 / 3
Workflow Clarity	The five instruction bullets are vague high-level phases with no specific sequencing, no validation checkpoints, and no feedback loops. There's no indication of what tools to run, what output to check, or how to recover from errors.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed content, which is a reasonable one-level-deep reference. However, no bundle files were provided, so the reference is unverifiable, and the SKILL.md itself provides almost no substantive content to serve as a useful overview.	2 / 3
	Total	6 / 12 Passed

Description

100%Scale 1-3

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 a concise capability statement followed by a 'Use when' clause, and occupies a well-defined niche around changelog and release note automation.

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' (explicit 'Use when' clause covering release workflows, release notes, and commit conventions).	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	Clearly occupies a distinct niche around changelog generation and release note automation. The specific mention of Keep a Changelog format, commits, PRs, and release workflows makes it unlikely to conflict with other skills like general git skills or CI/CD 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: popey/claude-code-skills
Path: plugins/antigravity-bundle-oss-maintainer/skills/changelog-automation/SKILL.md
Commit: a5a6601

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.