What problem does it solve? Shell-heavy tasks like git status, grep, find, and npm test produce verbose output that consumes large amounts of context tokens during repository exploration, leaving less room for actual reasoning and decision-making. ## Core Features & Use Cases - Command Routing: Maps common commands (cat, grep, find, git status/diff/log, npm test) to their RTK equivalents that return condensed output. - Clear Exclusion Rules: Keeps interactive prompts, streaming commands, verbatim evidence output, and piped commands on their original form so nothing breaks. - Graceful Fallback: If rtk is not on the PATH, the workflow continues with standard commands without blocking. - Use Case: When asked "where is function X?" or "show the branch status before committing", the agent runs rtk grep or rtk git status instead of the raw commands, getting decision-ready output at a fraction of the token cost. ## Quick Start Use the rtk-cli skill to inspect this repository's git status and search for a function without flooding the context with raw command output.
