debugging-hermes-tui-commands

Diagnose and fix Hermes TUI slash command issues across Python, gateway, and Ink layers.

78|16|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill debugging-hermes-tui-commands-sheawinkler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/sheawinkler/hermes-agent-ultra/tree/main/skills/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill debugging-hermes-tui-commands-sheawinkler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers diagnose and fix issues in Hermes TUI slash commands across Python backend, gateway, and Ink frontend.

Core Features & Use Cases

  • Cross-layer diagnosis: identify misalignments between Python command registry, gateway dispatch, and TUI slash handling.
  • Guided debugging workflow: provides structured steps to reproduce, inspect, and verify fixes across all layers.
  • Validation & rollback: includes verification steps and safe rollback guidance for production sessions.

Quick Start

Run Hermes in TUI mode and reproduce a failing slash command to observe registration, dispatch, and UI handling.

Frequently Asked Questions about debugging-hermes-tui-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do slash commands not appear in the TUI autocomplete?

Slash commands fail to appear in TUI autocomplete when the Python command registry is misaligned with the Ink frontend. Diagnose this cross-layer issue by inspecting command registration, gateway dispatch routing, and local TUI handler execution.

How do I debug slash commands that work inconsistently across CLI and TUI?

Debug inconsistent slash commands by running Hermes in TUI mode to reproduce the failure, then trace the command dispatch path through the gateway. Compare CLI and TUI handler execution to identify where the dispatch drops or misroutes the command.

What causes a slash command to fail dispatching through the gateway?

Gateway dispatch failures occur when the Python backend command registry and the gateway routing logic are out of sync. Inspect the gateway dispatch layer to verify that registered commands match the expected routing endpoints and local TUI handlers.

How do I verify and safely roll back a slash command fix in production?

Verify slash command fixes by reproducing the original failing command in TUI mode and confirming correct dispatch across the Python backend, gateway, and Ink frontend. Follow the provided structured rollback guidance to safely revert changes in production sessions.