rtk-ai/rtk

[rewrite] dotnet test|restore|format should auto-rewrite to rtk dotnet

Open

#1,830 opened on May 11, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clibuggood first issuepriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Summary

The proxies rtk dotnet test, rtk dotnet restore, and rtk dotnet format already exist (see rtk dotnet --help), but rtk rewrite only recognises dotnet build. As a result, the Claude Code hook silently passes through the other three subcommands.

Reproduction (rtk 0.39.0)

$ rtk rewrite "dotnet test"       ; echo $?
1
$ rtk rewrite "dotnet restore"    ; echo $?
1
$ rtk rewrite "dotnet format"     ; echo $?
1
$ rtk rewrite "dotnet build"      ; echo $?   # works
rtk dotnet build
0

Impact

rtk discover on a 30-day, 18k-command Claude Code history shows dotnet test = 263 calls and dotnet restore = 66 calls. None of them benefit from the existing proxy because the rewrite registry skips them.

Proposed fix

Extend the rewrite rule for dotnet in src/discover/registry.rs so it matches the subcommand set {build, test, restore, format} instead of only build. The output filter already handles all four — this is purely a routing fix.

Contributor guide

Research direction
Locate the rewrite rule for dotnet in src/discover/registry.rs, extend the match to include 'test', 'restore', and 'format' alongside 'build', and verify the output filter encompasses these subcommands.
Tech stack
rust
Domain
clideveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80