trace-command-execution

Tracing slash command execution tracks the full path from user input through registry lookup to handler completion, revealing exactly where execution fails. It inspects command parsing logic, registry state, and executor flow to resolve unresponsive handlers and incorrect command output.

Custom slash commands fail due to issues in parsing, registry state, handler logic, or event lifecycle. Tracing the execution path identifies the exact step causing the failure, allowing you to debug unhandled command handlers and resolve alias conflicts.

Debug alias conflicts and registry issues by inspecting the command registry state and executor flow during execution tracing. This reveals registration gaps and alias overlaps within the command system to resolve conflicting plugin behaviors.

Yes, you can trace the event lifecycle of a command handler to debug modal display issues. The Skill tracks execution from input parsing through handler execution, isolating the event lifecycle step where the modal display fails.

The best way to inspect command parsing logic is to trace the end-to-end execution path of the slash command. This monitors the transition from user input parsing to registry lookup, isolating the exact root cause of the system malfunction.