Add proxies for high-frequency git plumbing: git grep, git ls-tree
Author: GarciaTechBusinessCreated Jul 10, 2026Updated Sep 16, 2026
Labelsenhancementarea:clipriority:medium
Request
rtk discover TOP UNHANDLED (30-day scan, 34916 Bash commands) surfaces two git read commands with large, filterable output and no RTK proxy:
| Command | Count | Example |
|---|---|---|
git grep |
121 | git grep -l "resolveCostCenterByBranch…" |
git ls-tree |
73 | git ls-tree origin/main scripts/backfi… |
Both are high-token, low-signal for an LLM (long file lists / match dumps) — same profile as the already-proxied rtk grep / rtk find, which save 22–69%.
Why these two
Other unhandled entries (node --env-file, npm ci, ln -s, lsof -ti) are either tiny output or side-effecting — little to gain. git grep and git ls-tree are pure read commands whose output is exactly what RTK's filtering targets.
Suggestion
Route git grep through the existing rtk grep filter, and git ls-tree through the rtk ls/tree filter, preserving git flags.
rtk 0.42.2.
Source: rtk-ai/rtk