skills/wrap-loops/SKILL.md line 29 instructs the agent to run:
git ls-files --cocanonical --exclude-standard
--cocanonical is not a git flag, so Step 1 always fails:
$ git ls-files --cocanonical --exclude-standard
error: unknown option `cocanonical'
usage: git ls-files [<options>] [<file>...]
(git 2.52.0, but this isn't version-specific — the flag has never existed.)
Impact
Step 1 is the scan-target enumeration step. In a real git repo the command errors, and the agent either falls through to the find fallback documented for the non-git case or improvises. The find fallback does not respect .gitignore, which is the stated reason for preferring git ls-files in the first place, so gitignored files can end up in the candidate set.
Suggested fix
Looks like a typo. The intended behavior ("respects .gitignore automatically") matches:
git ls-files --cached --others --exclude-standard
which lists tracked plus untracked-but-not-ignored files. If only tracked files are wanted, plain git ls-files is enough and --exclude-standard is a no-op.
skills/wrap-loops/SKILL.mdline 29 instructs the agent to run:--cocanonicalis not a git flag, so Step 1 always fails:(git 2.52.0, but this isn't version-specific — the flag has never existed.)
Impact
Step 1 is the scan-target enumeration step. In a real git repo the command errors, and the agent either falls through to the
findfallback documented for the non-git case or improvises. Thefindfallback does not respect.gitignore, which is the stated reason for preferringgit ls-filesin the first place, so gitignored files can end up in the candidate set.Suggested fix
Looks like a typo. The intended behavior ("respects
.gitignoreautomatically") matches:which lists tracked plus untracked-but-not-ignored files. If only tracked files are wanted, plain
git ls-filesis enough and--exclude-standardis a no-op.