/test-routing
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
claude install-skill https://github.com/rtk-ai/rtk README
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
- undefined
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
Related Skills
Webapp Testing
When testing local web applications or verifying UI behaviorTest local web applications using Playwright for UI verification and debugging
Testing official #29
, [#52](https://github.com/affaan-m/everything-claude-code/issues/52), [#103](https://github.com/affaan-m/everything-claude-code/issues/103)). The behavior changed between Claude Code versions, leading to confusion. We now have a regression test to prevent this from being reintroduced.
Testing community Fix Issue
by metabase - Addresses GitHub issues by taking issue number as parameter, analyzing context, implementing solution, and testing/validating the fix for proper integration.
Testing community Pypict Test Design
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for optimized test suites
Testing community gstack
| 15,000+ | Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release Manager, and QA Engineer. 15K+ stars in 5 days. |
Testing community **playwright**
| claude-plugins-official | Browser automation, E2E testing, screenshots |
Testing community