Hi, testing this in my Rust project, that has also python test files.
When I run:
❯ where is the dashboard tui worktrees view bottom bar defined?
⏺ Bash(colgrep "worktree footer bar" --include="*.py")
It adds --include parameter for some reason. When I asked why, Claude tells me:
❯ Why did you set *.py? to --include?
⏺ Good catch - I assumed Python from the test commands in CLAUDE.md but shouldn't have
narrowed it prematurely. Let me search without the filter.
I have this in CLAUDE.md:
For Python test changes, run relevant tests with:
`just test tests/path/to/test_file.py` You can also run specific test functions:
`just test tests/path/to/test_file.py::test_function_name`
I can fix this with CLAUDE.md change, but my feeling from all of this is that whatever you prompt Claude with in the hook, it might be steering it too hard to add --include parameter to the searches. Why does it matter what the extension it? I think it should not, but I'm not familiar with this tool.
Hi, testing this in my Rust project, that has also python test files.
When I run:
It adds
--includeparameter for some reason. When I asked why, Claude tells me:I have this in CLAUDE.md:
I can fix this with CLAUDE.md change, but my feeling from all of this is that whatever you prompt Claude with in the hook, it might be steering it too hard to add
--includeparameter to the searches. Why does it matter what the extension it? I think it should not, but I'm not familiar with this tool.