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.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill changelog-automation79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 third person voice, includes natural trigger terms developers would use, and provides explicit 'Use when' guidance with multiple relevant scenarios.
| 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 on changelog/release note generation with distinct triggers like 'changelog', 'Keep a Changelog', 'release notes'. 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 provides excellent, actionable code examples for changelog automation but suffers from being overly comprehensive without proper organization. It presents too many parallel approaches without guidance on selection, and the content would benefit significantly from being split across multiple files with SKILL.md serving as an overview with clear navigation.
Suggestions
Split implementation methods into separate reference files (e.g., methods/semantic-release.md, methods/git-cliff.md) and keep only a quick-start example in SKILL.md
Add a decision matrix or flowchart at the top to help choose between the 6 methods based on project needs (Node.js vs Python, full automation vs manual, etc.)
Remove the 'Core Concepts' section explaining Conventional Commits and Semantic Versioning - Claude knows these; link to external specs instead
Add validation steps for the release workflow (e.g., 'verify changelog generated correctly before pushing tags')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose for its purpose. It includes 6 different implementation methods when 2-3 would suffice, and sections like 'Core Concepts' explain Conventional Commits and Semantic Versioning that Claude already knows well. | 2 / 3 |
Actionability | Excellent executable examples throughout - complete config files, bash commands, YAML workflows, and TOML configurations are all copy-paste ready. The code examples are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | While individual tool setups are clear, there's no guidance on which method to choose or when. The skill presents 6 parallel approaches without helping Claude decide between them or providing validation checkpoints for the release process itself. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. All 6 implementation methods, templates, and examples are inline when they could be split into separate reference files (e.g., SEMANTIC-RELEASE.md, GIT-CLIFF.md). | 1 / 3 |
Total | 8 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (581 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.