debugging-hermes-tui-commands

Debug Hermes TUI slash commands across Python, gateway, and Ink/TypeScript layers.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill debugging-hermes-tui-commands
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/ChangZhou-xj/zxj_skill/tree/main/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill debugging-hermes-tui-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes TUI slash commands can fall out of sync across Python backend, the TUI gateway, and the Ink/TypeScript frontend, leading to missing autocomplete entries and inconsistent behavior.

Core Features & Use Cases

  • Cross-layer debugging of slash commands across Python, gateway, and Ink UI.
  • Verify command registration, autocomplete data, and handler mappings in all layers.
  • Use case: diagnose a missing autocomplete entry for a new command and ensure it appears with the correct description and args.

Quick Start

Run hermes --tui and type / to trigger autocomplete, then test a problematic command to observe how the Python, gateway, and UI layers respond.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why do Hermes TUI slash commands fail in the terminal but work in the CLI?

Hermes TUI slash commands fail when the Python backend, TUI gateway, and Ink/TypeScript frontend fall out of sync. Cross-layer misalignment causes commands to work in the CLI but fail in the TUI due to inconsistent dispatch logic or missing UI handlers.

How do I debug missing autocomplete entries for slash commands in a TypeScript TUI?

Debug missing autocomplete entries by verifying command registration in the canonical Python registry, checking gateway mappings, and inspecting local Ink/TypeScript frontend handlers to ensure synchronized cross-layer command definitions.

What causes cross-layer misalignment in Python backend and TypeScript frontend command registries?

Cross-layer misalignment occurs when new commands are added to the Python backend but the TUI gateway dispatch logic and Ink/TypeScript frontend command definitions are not updated with the correct descriptions and args.

How do I synchronize slash command handlers across Python, gateway, and Ink UI layers?

Synchronize slash command handlers by inspecting the canonical command registry in Python, verifying gateway dispatch logic, and updating local TUI handlers in the Ink/TypeScript frontend to enforce cross-layer consistency.

Can I use this skill to diagnose TUI command dispatch logic without modifying the Python backend?

Yes, you can diagnose gateway dispatch logic and local TUI handlers independently. However, fixing missing autocomplete entries or inconsistent behavior often requires applying synchronized changes across the Python backend, gateway, and frontend.