Skip to content

Conversation

@technicalpickles
Copy link
Owner

Summary

  • Simplifies test-claude from 6 commands to 1
  • Auto-detects and installs all plugins with .claude-plugin/ directories
  • Removes --setup, --install, --status, --reset flags (only --clean remains)

Before

./bin/test-claude --setup
./bin/test-claude --install tool-routing
./bin/test-claude --install git
./bin/test-claude --install ci-cd-tools
./bin/test-claude --install dev-tools
./bin/test-claude

After

./bin/test-claude  # setup + install all + run claude

For validation without interactive session:

./bin/test-claude -p ""  # exits immediately after setup

Test plan

  • ./bin/test-claude --help shows simplified usage
  • ./bin/test-claude --clean removes test config
  • ./bin/test-claude -p "" sets up config and exits
  • CLAUDE_CONFIG_DIR=... tool-routing list shows 5 sources
  • CLAUDE_CONFIG_DIR=... tool-routing test passes (32 tests)

🤖 Generated with Claude Code

technicalpickles and others added 4 commits February 2, 2026 17:12
…very

Update documentation to reflect the new manifest-driven route discovery:

- Replace CLAUDE_PLUGINS_DIR with CLAUDE_PROJECT_ROOT
- Document exact projectPath matching for local-scoped plugins
- Add troubleshooting for "fewer sources than expected" issue
- Update environment variables table

The old filesystem-based discovery using CLAUDE_PLUGINS_DIR no longer
applies. Discovery now uses `claude plugin list --json` which filters
local-scoped plugins by exact projectPath match.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add Quick Validation section using test-claude for reliable, isolated
testing that doesn't affect user's plugin state. This approach:

- Installs all plugins with routes from local repo
- Uses isolated CLAUDE_CONFIG_DIR
- Avoids project path matching issues
- Tests the actual discovery path Claude Code uses

Also reorganized Step 3 into three options:
- Option A: test-claude (recommended)
- Option B: TOOL_ROUTING_ROUTES (explicit, no discovery)
- Option C: user's enabled plugins (variable results)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Collapse the 6-step test-claude workflow into a single command:

Before:
  ./bin/test-claude --setup
  ./bin/test-claude --install tool-routing
  ./bin/test-claude --install git
  ./bin/test-claude --install ci-cd-tools
  ./bin/test-claude --install dev-tools
  ./bin/test-claude

After:
  ./bin/test-claude

The script now:
- Auto-detects all plugins with .claude-plugin/ directories
- Sets up config and installs everything on first run
- Skips setup on subsequent runs (config already exists)
- Only flag is --clean to remove test config

For validation without interactive session, use:
  ./bin/test-claude -p ""

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@technicalpickles technicalpickles merged commit 941b38c into main Feb 3, 2026
1 check passed
@technicalpickles technicalpickles deleted the feat/simplify-test-claude branch February 3, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant