changelog-generator

Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, highly actionable body that leverages real bundle scripts and one-level-deep references effectively. It loses points for mild section redundancy, a dead README.md reference, and validation checkpoints that live in a separate section rather than inline in each workflow.

Suggestions

Remove the broken [README.md](README.md) reference from the References list — the file does not exist in the bundle.

Consolidate the overlapping advisory sections (Common Pitfalls, Best Practices, Output Quality Checks, CI Policy) into a single concise list to reduce token redundancy.

Add an inline validate->fix->retry checkpoint within the changelog-writing workflow (e.g., lint -> generate draft -> review/approve -> only then --write CHANGELOG.md) so the feedback loop is explicit per workflow, not just in Release Governance.

Dimension	Reasoning	Score
Conciseness	Content is mostly lean and operational without explaining concepts Claude already knows, but 'When to Use' duplicates the description's triggers and the advisory lists (Common Pitfalls, Best Practices, Output Quality Checks, CI Policy) overlap thematically and could be tightened.	4 / 5
Actionability	Workflows 1-5 provide copy-paste-ready commands with real script paths and flags (generate_changelog.py, version_bumper.py, commit_linter.py), covering the common cases of git-range, stdin, write, version computation, and linting.	5 / 5
Workflow Clarity	Workflows are sequenced and the Release Governance checklist supplies validation gates ('Validate semver bump recommendation', 'Tag release only after changelog is approved') plus a Failure Handling section, but no inline validate->fix->retry loop appears within the individual workflows.	4 / 5
Progressive Disclosure	Good overview-to-reference structure with one-level-deep links to real bundle files (ci-integration.md, monorepo-strategy.md, hotfix-procedures.md, scripts/), but the References list includes [README.md](README.md) which does not exist in the bundle, a dead link.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities, gives explicit 'Use when' triggers with natural user phrasings, and carves out a distinct niche. It matches the top anchors across all four dimensions.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'commit parsing, semantic-bump logic, and changelog rendering' plus release-note generation — giving comprehensive coverage rather than generic phrasing.	5 / 5
Completeness	Explicitly states what it does ('Produce consistent, auditable release notes from Conventional Commits') and when to use it ('Use when cutting a release...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user phrasings ('cutting a release', 'what version bump do these commits require', 'we need an emergency hotfix process') alongside synonyms like CHANGELOG.md, semantic version, and hotfix/rollback.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Conventional Commits / release management) with distinct triggers unlikely to fire for unrelated skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: engineering/skills/changelog-generator/SKILL.md
Commit: 19392f7

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