supp

Read source files with dependency context — use INSTEAD OF the Read tool when you need file contents plus imports/exports/dependency graph. TRIGGER when: you need to read, view, or understand any source code file (.rs, .py, .js, .ts, .go, .c, .cpp, .java, etc.), before editing a source file, or when the user asks to look at code. DO NOT TRIGGER when: reading non-code files (.toml, .json, .md, .yaml, .lock, .txt, .env)

Visualize file-level import/dependency graph — use when you need to understand what a module depends on or what depends on it. TRIGGER when: you need to understand file-level dependencies, what imports what, or assess blast radius of changing a module. DO NOT TRIGGER when: you need symbol-level dependencies (use /why) or just need to read file contents (use /ctx)

Review git changes: staged, unstaged, or branch diffs with full patches — use INSTEAD OF git diff in Bash when reviewing work or preparing commits. TRIGGER when: you need to see what changed, review diffs, check staged/unstaged changes, or prepare a commit message. DO NOT TRIGGER when: you need project structure (use /tree) or need to understand code logic (use /why or /ctx)

Find symbol definitions by name with ranked results — use INSTEAD OF Grep/Glob when locating functions, types, structs, traits, or constants. TRIGGER when: you need to find where a function, type, struct, trait, class, constant, or variable is defined, or locate a symbol by name in the codebase. DO NOT TRIGGER when: searching for arbitrary text patterns, log messages, config values, or string literals (use Grep for those)

Show directory layout with git status — ONLY for project structure or file location questions, not for understanding code or reviewing changes. TRIGGER when: you need to see project structure, directory layout, what files exist, or orient yourself in an unfamiliar codebase. DO NOT TRIGGER when: you need to read file contents (use /ctx), find symbols (use /sym), or review changes (use /diff)