rtk-ai / rtk-ai/rtk

rtk discover: python/python3, git checkout, sha256sum/md5sum, cat, stat, lsof, pgrep not recognized

Open
#3,443 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:cli enhancement help wanted priority:medium
Dominant language
Rust
Stars
81.1k
Forks
5.1k
Avg merge
4d 21h
Merged PRs (30d)
35

Description

Context

Ran rtk discover against 40 local Claude Code sessions (last 30 days, 7631 Bash commands). It found 3690 commands with existing rtk equivalents that weren't being routed through rtk (~722.5K tokens saveable), plus a separate list of commands with no rtk equivalent at all yet.

Top unhandled commands (from rtk discover output)

Command Count (30d sample) Example
python / python3 306 ad-hoc scripts, heredocs (python3 - <<'EOF')
git checkout 92 git checkout -- cache/queue.json
sha256sum / md5sum ~71 checksum verification over log/storage files
cat 20 appending/reading file contents
stat 17 stat -c '%y' file
lsof 10 lsof -i :8000
pgrep 13 pgrep -af "pytest -q"
until ! / echo loops ~75 polling loops (until ! kill -0 PID; do sleep; done)

python/python3 alone looks like the largest single opportunity — mostly short ad-hoc scripts and heredocs whose stdout is currently passed through uncompressed.

Ask

Would a wrapper for python/python3 (at least for common patterns like -c, heredoc, and script execution with verbose stdout) be in scope? Happy to share anonymized command samples if useful for shaping the matcher.

Also noticed some already-supported commands (git status, find, grep -n, tail -n) show up in the "missed savings" list from historical sessions even though live testing now confirms the hook does rewrite them correctly today — so that part may just be stale data from before those integrations existed, not a current bug. Flagging in case it's useful signal anyway.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the rtk discover output and the existing hook integrations for commands such as git status, find, grep -n, and tail -n. Review how command matching handles python/python3, then use the listed -c, heredoc, and script-execution samples to define the wrapper scope. Done means supported patterns are recognized without treating unrelated historical missed-savings data as a current bug.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.