Unverified50% confidenceFactExact time
Fixed an issue where skills configured per directory and defined with paths: could not be found after cd-ing into a deeper directory in a git repository in Bash.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/27/2026
First Seen
Valid until: 1/25/2027
Sources
Related Entities
Related Claims
UnverifiedThis update fixes a permission bypass on Windows where, when Git Bash was missing and the hook command was only a quoted string, the PreToolUse and PermissionRequest hooks incorrectly allowed tool calls.61% similarUnverifiedThe root cause of a command not found error is that the system PATH environment variable does not include the directory where the tool's executable file is located.60% similarUnverifiedClaude Code checkpoints do not record files changed by terminal commands or content manually modified by the user, and therefore cannot replace Git.58% similarUnverifiedWhen running `claude -p "/usage"` from Git Bash, `/usage` is parsed as a file path and sent to the model as a prompt, so clawd-usage-winwidget is restricted to invoking this command only from PowerShell.57% similarUnverifiedThe root cause of ~ sometimes working and sometimes failing in PATH is that it can only be expanded when some intermediate link happens to invoke the shell to handle it.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1105251API
curl https://kongchang.com/api/v1/knowledge/claims/1105251MCP
get_claim(id=1105251)