BD release-notes-drafter
Drafts release notes from the merged pull requests since the last git tag. Use when a maintainer asks for a changelog entry, release notes, or a summary of what changed since the previous release.
The skill extracts commits between the last git tag and HEAD, assembling release notes from merged pull requests. Promises to automate changelog writing and save maintainers time on gathering PR summaries.
One file, clean syntax, no critical errors. Grade B indicates the logic works but has minor rough edges: process score of 48 suggests gaps in documentation or usage examples. Not tested in sandbox. Platform coverage is broad across all major AI assistants.
Install if you maintain a repo with frequent releases and tire of manually compiling notes. Overkill for one-off use.
Drafts release notes from the merged pull requests since the last git tag.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 97 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 196: enough signal without eating the budget
- +3Step-by-step instructions: 4 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.