BC git-commit-message-generator
Generate conventional commit messages by analyzing staged changes automatically
Generate conventional commit messages by analyzing staged changes automatically
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
AnalyzerGitHubSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 313): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 53 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
- 60Steps. 98 steps, 4 vague phrases
- 70When it triggers. States when to use, but not when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3715 tokens
- 100Progress reporting. Reports progress
- low 16 top-level sections: this looks like several domains in one skill
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)
- +3Description length 79: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 55 headings
- +3Step-by-step instructions: 98 items
- +4Has examples (37 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: clean
This is a documentation-only skill for drafting conventional commit messages from staged Git diffs, with disclosed optional tooling setup risks but no hidden or automatic harmful behavior found.
LLM: benign (high) · VirusTotal: · 16 Sept 2026