skills/commitlore-query/SKILL.md:53:
All four take zero or more paths (commitlore context a.ts b.ts answers for both), follow renames, and share these flags
Run exactly that:
$ commitlore context src/core/types.ts src/core/grade.ts --no-index
commitlore: git log --follow accepts exactly one pathspec, so renames are not
followed for 2 paths; query one path at a time to follow its rename chain
The CLI is right and says so clearly. The skill states the opposite as a property of the command, in the same sentence that recommends the multi-path form.
Why this one matters more than a doc typo
Skills are the artifact that teaches an agent how to use this tool. An agent that reads this sentence will batch paths — which is the efficient-looking thing to do — and receive an answer that silently omits every record attached to a file's earlier name.
The omission is invisible at the call site. The agent gets a well-formed answer with fewer records in it, and nothing in the output it acts on distinguishes "no records" from "records exist under the previous filename". The CLI's warning goes to stderr; inject and the skill flow do not surface it.
Sixth instance of the same shape: an answer that does not carry what it could not see (#58, #60, #63, #66, #67).
Fix
Correct the sentence: multi-path answers do not follow renames, and a rename-sensitive query must be one path per call. Then check the other two skills for claims of the same kind — I only audited this one, and commitlore-commits and commitlore-setup were not read line by line against behaviour.
Worth considering separately: whether context should refuse multiple paths outright rather than degrade. A warning that the caller cannot see is close to no warning.
skills/commitlore-query/SKILL.md:53:Run exactly that:
The CLI is right and says so clearly. The skill states the opposite as a property of the command, in the same sentence that recommends the multi-path form.
Why this one matters more than a doc typo
Skills are the artifact that teaches an agent how to use this tool. An agent that reads this sentence will batch paths — which is the efficient-looking thing to do — and receive an answer that silently omits every record attached to a file's earlier name.
The omission is invisible at the call site. The agent gets a well-formed answer with fewer records in it, and nothing in the output it acts on distinguishes "no records" from "records exist under the previous filename". The CLI's warning goes to stderr;
injectand the skill flow do not surface it.Sixth instance of the same shape: an answer that does not carry what it could not see (#58, #60, #63, #66, #67).
Fix
Correct the sentence: multi-path answers do not follow renames, and a rename-sensitive query must be one path per call. Then check the other two skills for claims of the same kind — I only audited this one, and
commitlore-commitsandcommitlore-setupwere not read line by line against behaviour.Worth considering separately: whether
contextshould refuse multiple paths outright rather than degrade. A warning that the caller cannot see is close to no warning.