Globs, Types, and Ignore Rules

Use glob filters when file types alone are too broad or when you want path-specific targeting.

Excluding generated assets reduces noise and speeds up scans.

This is helpful in monorepos that contain both source and build outputs.

Multiple globs give precise control without editing ignore files.

`--debug` is the fastest way to understand why an expected file did not appear.

Type filters are easier to read and reuse than complex globs.

This is useful when docs generate too much noise during code-focused searches.

Custom types are ideal for proprietary extensions or mixed conventions.

The custom definition only applies to this invocation unless you put it in config.

This is useful before deciding whether to use `-t`, `--glob`, or a custom type.

By default, hidden files are skipped to reduce surprise and noise.

This is useful when investigating generated files or vendored code that ignore rules normally hide.

`-uuu` is the blunt-force mode for exhaustive audits.

This can be important in workspaces that use symlink-based dependency managers.

Great for personal workspace exclusions that you do not want to commit.