rtk-ai/rtk

cargo nextest rewrite rule missing from registry despite subcommand existing

Open

#2,046 opened on May 22, 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

Bug

rtk cargo nextest exists as a valid subcommand with its own filtered output, but rtk rewrite "cargo nextest run" returns exit code 1 (no RTK equivalent), so the Claude Code hook never rewrites cargo nextest calls to use RTK.

Steps to reproduce

# Subcommand exists:
rtk cargo nextest --help   # works fine

# But rewrite rule is missing:
rtk rewrite "cargo nextest run"
echo $?  # → 1

Expected behavior

rtk rewrite "cargo nextest run" should return rtk cargo nextest run (exit 0), so the Claude Code PreToolUse hook transparently rewrites cargo nextest invocations for token savings.

Environment

  • rtk 0.40.0
  • Hook: rtk hook claude / rtk-rewrite.sh (hook-version 3)

Notes

The fix is likely a missing entry in src/discover/registry.rs for the cargo nextest rewrite rule — the subcommand implementation already exists, only the rewrite registration is absent.

Contributor guide