rtk-ai/rtk

[proxy] add rtk dotnet wrappers for run, ef, user-secrets, nuget, tool

Open

#1,831 opened on May 11, 2026

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

Repository metrics

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

Description

Use case

For .NET developers using Claude Code, dotnet build/test/restore/format are already proxied. The following subcommands are equally output-heavy but lack proxies:

Subcommand Why it's noisy
dotnet run Build banner + application stdout/log noise
dotnet ef … "Build started…/Build succeeded" header + verbose migration info
dotnet user-secrets list JSON dump with whitespace
dotnet nuget list/search Padded tables
dotnet tool list Padded tables

Frequency (30-day Claude Code history via rtk discover)

  • dotnet run: 39
  • dotnet user-secrets: 36
  • dotnet ef: dominant in EF-Core-heavy projects (not in default discover sample but ubiquitous in .NET stacks with migrations)

Suggested approach

A shared MSBuild-banner stripper plus per-subcommand filters analogous to rtk dotnet build. The ef filter should also strip the duplicate build preamble that EF emits before the actual migration output.

Contributor guide

Research direction
Study the existing `rtk dotnet build` proxy implementation and replicate pattern for run, ef, user secrets, nuget, tool. Focus on the shared MSBuild banner stripper and per subcommand output filters.
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.
2
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
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75