validate

Validate Tool-Routing Plugin

Run these steps to verify the tool-routing plugin is correctly installed and working.

Monorepo Context

This plugin is part of the pickled-claude-plugins monorepo. Routes are contributed by multiple plugins:

Plugin	Route Location	Routes
tool-routing	hooks/tool-routes.yaml	bash-cat-heredoc, bash-echo-*, tool-routing-manual-test
dev-tools	hooks/tool-routes.yaml	atlassian
git	skills/pull-request/tool-routes.yaml	github-pr
buildkite	tool-routes.yaml	buildkite

Quick Validation (Isolated Environment)

Use test-claude to validate in an isolated environment without affecting your normal Claude config:

# From repo root - sets up config, installs all plugins, starts claude
./bin/test-claude

# Or run validation commands in the isolated env
CLAUDE_CONFIG_DIR="$PWD/tmp/test-claude-config" \
  uv run --directory plugins/tool-routing tool-routing list

# Should show: "Routes (merged from 4 sources)"

Use ./bin/test-claude --clean to remove the test config and start fresh.

This approach:

• Doesn't modify your user plugin state
• Installs plugins from local source (not marketplace cache)
• Tests the actual discovery path Claude Code uses

Step 1: Validate Plugin Manifests

Run claude plugin validate on each plugin with a manifest:

# From repo root
for plugin in plugins/*/; do
  if [ -d "$plugin/.claude-plugin" ]; then
    echo "=== Validating $plugin ==="
    claude plugin validate "$plugin"
  fi
done

Step 2: Run Plugin Structure Tests

The plugin includes pytest tests that validate hooks.json format:

cd plugins/tool-routing
uv run pytest tests/test_plugin_structure.py -v

These tests catch silent failures where hooks.json is valid JSON but wrong format:

Wrong Format	Correct Format
"hooks": [...] (array)	"hooks": {"PreToolUse": [...]} (object keyed by event)
"matcher": {"tool_name": "X"}	"matcher": "X" (string pattern)
"type": "preToolUse"	"type": "command"
$CLAUDE_PLUGIN_ROOT	${CLAUDE_PLUGIN_ROOT} (with braces)