rtk-ai/rtk

feat: Extend git subcommand coverage (ls-files, rm, tag)

Open

#1526 opened on Apr 25, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
effort-mediumenhancementgood first issue

Description

The rtk git handler covers diff, status, log, add, stash, show, branch, worktree, fetch, pull, push — but misses several commonly-used subcommands.

Currently not intercepted:

$ rtk hook check "git ls-files"     # → exit 1, no rewrite ✗
$ rtk hook check "git rm"           # → exit 1, no rewrite ✗
$ rtk hook check "git tag"          # → exit 1, no rewrite ✗
$ rtk hook check "git cherry-pick"  # → exit 1, no rewrite ✗
$ rtk hook check "git rebase"       # → exit 1, no rewrite ✗
$ rtk hook check "git merge"        # → exit 1, no rewrite ✗
$ rtk hook check "git checkout"     # → exit 1, no rewrite ✗

Highest value:

  • git ls-files (98 calls/month) — in monorepos this can return hundreds of paths. Compact tree output (like rtk find) would be ideal.
  • git rm (92 calls/month) — bulk deletes produce one rm 'path' line per file. Summary format would help.

Lower priority (write operations where full output matters for confirmation):

  • git cherry-pick, git rebase, git merge, git checkout — these have important status output but could still benefit from ANSI stripping.

Usage context: ~280 calls/month for the missing subcommands, primarily in a 12-service monorepo with Claude Code.

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingGit knowledgeRTK project setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the existing git handler implementation, likely in `src/handlers/git.rs`. Study how currently supported subcommands (diff, status, log, etc.) are intercepted and rewritten. Then implement handling for missing subcommands: `ls files`, `rm`, `tag`, `cherry pick`, `rebase`, `merge`, `checkout`. Prioritize `ls files` and `rm` per usage data. Test with `rtk hook check` to verify rewrites. Consider different output formats: compact tree for `ls files`, summary for `rm`. Review any existing tests for patterns.