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.
85
Quality
78%
Does it follow best practices?
Impact
99%
1.30xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/changelog-automation/SKILL.mdQuality
Discovery
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 well-crafted skill description that follows best practices. It specifies concrete actions (changelog generation from multiple sources), uses natural developer terminology, includes an explicit 'Use when...' clause with clear triggers, and carves out a distinct niche around release documentation workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Automate changelog generation from commits, PRs, and releases' and specifies the format standard 'Keep a Changelog format'. These are concrete, actionable capabilities. | 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'changelog', 'commits', 'PRs', 'releases', 'release workflows', 'release notes', 'commit conventions'. Good coverage of terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on changelog generation and release workflows. The combination of 'changelog', 'Keep a Changelog format', and 'release notes' creates distinct triggers unlikely to conflict with general git or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, appropriately delegating detailed content to a separate resource file. However, it severely lacks actionability - the instructions are too abstract to be useful without concrete examples, specific tool recommendations, or executable commands. The skill tells Claude what to do conceptually but not how to do it practically.
Suggestions
Add concrete tool examples (e.g., conventional-changelog, release-please, semantic-release) with actual configuration snippets or commands
Include at least one executable example showing how to generate a changelog entry from a commit
Add specific commit message format examples showing input commits and expected changelog output
Include a validation step such as 'Run `npx conventional-changelog -p angular` and verify output before publishing'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands concepts like conventional commits and semantic versioning without explaining them. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Select a changelog format', 'Configure tooling') with no concrete code, commands, or specific tool examples. There's nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence but lack specificity and validation checkpoints. No concrete validation steps or feedback loops for error recovery are provided. | 2 / 3 |
Progressive Disclosure | Clear structure with a concise overview and well-signaled one-level-deep reference to the implementation playbook for detailed patterns and examples. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
9c177eb
- Reviewed
Table of Contents
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.