change-log-generator
Generates a structured CHANGELOG.md from VCS history and PR/issue references, categorized by change type. Use when cutting a release, when the user asks to update CHANGELOG.md, or when backfilling a changelog from git history.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill change-log-generator100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 excels across all dimensions. It provides specific capabilities (structured changelog generation from VCS/PR/issue data), includes natural trigger terms users would actually say, and explicitly states both what the skill does and when to use it. The focus on CHANGELOG.md specifically makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generates a structured CHANGELOG.md', 'from VCS history and PR/issue references', 'categorized by change type'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Generates a structured CHANGELOG.md from VCS history and PR/issue references, categorized by change type') and when ('Use when cutting a release, when the user asks to update CHANGELOG.md, or when backfilling a changelog from git history'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CHANGELOG.md', 'release', 'changelog', 'git history'. Covers common variations like 'cutting a release', 'update CHANGELOG.md', and 'backfilling a changelog'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on CHANGELOG generation with distinct triggers like 'CHANGELOG.md', 'cutting a release', and 'git history'. Unlikely to conflict with other documentation or git-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices: lean prose, concrete examples, clear workflow, and practical edge case handling. The transformation tables showing commit→changelog rewrites are particularly effective. The 'Do not' section provides clear guardrails without being preachy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No explanation of what a changelog is conceptually or how git works. Tables are dense and scannable. The audience split table efficiently distinguishes this skill from a related one without verbose explanation. | 3 / 3 |
Actionability | Provides exact git commands, concrete classification rules with specific commit message signals, transformation examples showing input→output, and a complete worked example with real commits becoming real changelog entries. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (delimit range → classify → rewrite) with explicit rules at each stage. Edge cases cover common failure modes. The 'Do not' section acts as validation guardrails preventing common mistakes. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to steps to examples to edge cases. References the related `release-notes-writer` skill appropriately. Content is appropriately sized for a single file without needing external references. | 3 / 3 |
Total | 12 / 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.
- 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.