/test-routing banner
rtk-ai rtk-ai

/test-routing

Testing community intermediate

Description

Vérifie le routing de commandes RTK sans exécution (dry-run). Utile pour tester si une commande a un filtre disponible avant de l'exécuter.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for rtk-ai/rtk, shared by 9 entries in this directory. It describes the repository, not this entry specifically.


model: haiku description: Test RTK command routing without execution (dry-run) - verifies which commands have filters

/test-routing

Vérifie le routing de commandes RTK sans exécution (dry-run). Utile pour tester si une commande a un filtre disponible avant de l'exécuter.

Usage

/test-routing  [args...]

Exemples

/test-routing git status
# Output: ✅ RTK filter available: git status → rtk git status

/test-routing npm install
# Output: ⚠️  No RTK filter, would execute raw: npm install

/test-routing cargo test
# Output: ✅ RTK filter available: cargo test → rtk cargo test

Quand utiliser

  • Avant d'exécuter une commande: Vérifier si RTK a un filtre
  • Debugging hook integration: Tester le command routing sans side-effects
  • Documentation: Identifier quelles commandes RTK supporte
  • Testing: Valider routing logic sans exécuter de vraies commandes

Implémentation

Option 1: Check RTK Help Output

COMMAND="$1"
shift
ARGS="$@"

# Check if RTK has subcommand for this command
if rtk --help | grep -E "^  $COMMAND" >/dev/null 2>&1; then
    echo "✅ RTK filter available: $COMMAND $ARGS → rtk $COMMAND $ARGS"
    echo ""
    echo "Expected behavior:"
    echo "  - Command will be filtered through RTK"
    echo "  - Output condensed for token efficiency"
    echo "  - Exit code preserved from original command"
else
    echo "⚠️  No RTK filter available, would execute raw: $COMMAND $ARGS"
    echo ""
    echo "Expected behavior:"
    echo "  - Command executed without RTK filtering"
    echo "  - Full command output (no token savings)"
    echo "  - Original command behavior unchanged"
fi

Option 2: Check RTK Source Code

COMMAND="$1"
shift
ARGS="$@"

# List of supported RTK commands (from src/main.rs)
RTK_COMMANDS=(
    "git"
    "grep"
    "ls"
    "read"
    "err"
    "test"
    "log"
    "json"
    "lint"
    "tsc"
    "next"
    "prettier"
    "playwright"
    "prisma"
    "gh"
    "vitest"
    "pnpm"
    "ruff"
    "pytest"
    "pip"
    "go"
    "golangci-lint"
    "docker"
    "cargo"
    "smart"
    "summary"
    "diff"
    "env"
    "discover"
    "gain"
    "proxy"
)

# Check if command in supported list
if [[ " ${RTK_COMMANDS[@]} " =~ " ${COMMAND} " ]]; then
    echo "✅ RTK filter available: $COMMAND $ARGS → rtk $COMMAND $ARGS"
    echo ""

    # Show filter details if available
    case "$COMMAND" in
        git)
            echo "Filter: git operations (status, log, diff, etc.)"
            echo "Token savings: 60-80% depending on subcommand"
            ;;
        cargo)
            echo "Filter: cargo build/test/clippy output"
            echo "Token savings: 80-90% (failures only for tests)"
            ;;
        gh)
            echo "Filter: GitHub CLI (pr, issue, run)"
            echo "Token savings: 26-87% depending on subcommand"
            ;;
        pnpm)
            echo "Filter: pnpm package manager"
            echo "Token savings: 70-90