Content
80%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable skill body: concrete dual-shell commands, a complete config example, and explicit graceful-degradation behavior. Its main gaps are the absence of any post-commit verification for what is a batch git operation, and a Behavior section that over-documents the script's internal logic relative to what the invoker needs.
Suggestions
Add a post-commit validation step (e.g., run `git log -1 --stat` or check the commit exit code) with an error-recovery path if the commit fails, to satisfy the batch-operation validation requirement.
Trim the Behavior section to the 2-3 facts the invoker needs (config-gated, event-keyed, default-off) and leave the script's internal lookup order to the script itself.
State how to determine the event name from the hook context with one concrete example invocation, since that is the only input Claude must derive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-organized with no padding or explanations of concepts Claude already knows, but the six-item "Behavior" section documents the script's internal logic (config lookup, fallbacks, message selection) that Claude does not need in order to simply invoke it, and "Automatically stage and commit all changes..." restates the description. This is 'efficient; minor instances of over-explanation that could be trimmed', not 5 where every token earns its place. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands are given for both Bash (`.specify/extensions/git/scripts/bash/auto-commit.sh <event_name>`) and PowerShell, with the placeholder substitution explicitly explained and concrete event examples (`after_specify`, `before_plan`, `after_implement`). The configuration YAML is complete and concrete, covering the common cases. | 5 / 5 |
Workflow Clarity | The sequence (determine event name, run script) is clear and precondition failures are handled ("If Git is not available... skips with a warning"), but the core operation `git add .` + `git commit` is a batch operation with no validation or verification step — no check that the commit succeeded, no inspection of the result, no error-recovery loop. Per the judging guidelines, a batch skill without validation cannot score above 3. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, needs no external references, and is organized into clear, well-labeled sections (Behavior, Execution, Configuration, Graceful Degradation). Per the simple-skill guideline, this earns a 5; the referenced script and config paths are target-project files, appropriately pointed to rather than inlined. | 5 / 5 |
Total | 17 / 20 Passed |