Stats
Actions
Tags
From turboshovel
If you're reading this, the plugin is working. This command triggered the `SessionStart` hook.
How this command is triggered — by the user, by Claude, or both
Slash command
/turboshovel:testThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Turboshovel Plugin Test If you're reading this, the plugin is working. This command triggered the `SessionStart` hook. ## Verify in Logs Check the turboshovel log to confirm: You should see a `SessionStart` entry from when this session started. ## Quick Checks | Check | How | |-------|-----| | Plugin loaded | Run `/plugin` - no turboshovel errors | | Hooks firing | Check logs for `HOOK_INVOKED` entries | | Gates config | `cat .claude/gates.json` | ## Troubleshooting | Symptom | Fix | |---------|-----| | Plugin errors | Check `~/.claude/debug/latest` | | No log entries | Ensure `...
If you're reading this, the plugin is working. This command triggered the SessionStart hook.
Check the turboshovel log to confirm:
# Tail logs (in a separate terminal)
mise run logs
# or: tail -f ~/.turboshovel/turboshovel.log
You should see a SessionStart entry from when this session started.
| Check | How |
|---|---|
| Plugin loaded | Run /plugin - no turboshovel errors |
| Hooks firing | Check logs for HOOK_INVOKED entries |
| Gates config | cat .claude/gates.json |
| Symptom | Fix |
|---|---|
| Plugin errors | Check ~/.claude/debug/latest |
| No log entries | Ensure TURBOSHOVEL_LOG is not set to 0 |
| Gates not firing | Create .claude/gates.json |
npx claudepluginhub tobyhede/turboshovel --plugin turboshovel/validateValidates tool-routing plugin installation and hooks format via manifest checks, pytest structure tests, and route pattern matching in isolated monorepo environment.
/add-hookAdds or updates hooks.json with a new hook configuration for automated plugin behavior at lifecycle events like PreToolUse or SessionStart. Requires event type; optional matcher and --plugin.
/create-hookScaffolds, debugs, validates, and analyzes Claude Code hooks with built-in templates and conflict detection.
/create-pluginGuides end-to-end creation of Claude Code plugins via phased workflow: discover requirements, plan components like skills/agents/hooks, implement, validate, and test.
/testTests if the autorun plugin is properly loaded and working, confirming plugin functionality in Claude Code.
/health-checkValidates plugin agents, hooks, and commands, reporting PASS/FAIL status for each component type with overall health summary.