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.
48
50%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/documentation-generation/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 strong skill description that concisely covers specific capabilities, includes natural trigger terms, and provides explicit 'Use when' guidance. It uses proper third-person voice and clearly carves out a distinct niche around changelog and release note automation. The description is well-structured and follows best practices closely.
| 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 | Occupies a clear niche around changelog generation and release note automation. The specific mention of Keep a Changelog format, commits, PRs, and release workflows makes it highly distinguishable from general git, CI/CD, or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill fails on nearly every dimension. It claims to be about changelog automation but provides no actual automation tooling, commands, or executable workflows. The content is padded with concepts Claude already knows (Conventional Commits format, Keep a Changelog), includes a bloated example changelog template that isn't instructive, and references a non-existent bundle file. It reads more like a blog post introduction to changelogs than an actionable skill.
Suggestions
Add executable automation setup: include specific CLI commands (e.g., `npx conventional-changelog -p angular -i CHANGELOG.md -s`), commitlint configuration files, and a GitHub Actions workflow YAML for automated release notes.
Remove the verbose changelog template and best practices lists; replace with a concise format specification and a concrete end-to-end workflow (install tools → configure → validate commits → generate changelog → release).
Add validation checkpoints: e.g., 'Run `npx commitlint --from HEAD~1` to verify commit format before pushing' and 'Preview changelog with `--dry-run` before committing changes.'
Either provide the referenced `references/details.md` bundle file or remove the reference; ensure any cross-references point to real, accessible files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows. It explains what Keep a Changelog is, what Conventional Commits are, and includes generic best practices ("Write clear messages - Future you will thank you") that add no actionable value. The lengthy release notes template with sections like 'Known Issues' and 'Dependencies Updated' is excessive filler rather than targeted instruction. | 1 / 3 |
Actionability | Despite being about 'automation,' the skill provides no executable code, no tool commands, no CI configuration snippets, and no actual automation setup. It shows example commit messages and a changelog template but never instructs how to generate changelogs automatically (e.g., no conventional-changelog CLI commands, no GitHub Actions workflow, no commitlint config). It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow for setting up changelog automation. The skill lacks any step-by-step process—no 'install X, configure Y, run Z' sequence. For a skill about automating changelog generation, there should be a clear multi-step workflow with validation, but none exists. | 1 / 3 |
Progressive Disclosure | The skill references `references/details.md` but no bundle files are provided, making this a dead reference. The content is a monolithic wall mixing a changelog template, commit examples, and best practices without clear structure or navigation. The reference to details.md is buried inside a markdown code block, making it even more confusing. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
cf6059d
- 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.