debugging-hermes-tui-commands

Diagnose and fix missing or misregistered Hermes TUI slash commands across Python, gateway, and Ink frontend.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps identify and resolve issues where slash commands in the Hermes TUI are missing, misregistered, or inconsistent across Python CLI backend, gateway dispatch, and Ink frontend.

Core Features & Use Cases

  • Investigate command presence in Python backend COMMAND_REGISTRY, ensure gateway known commands, and frontend slash handlers.
  • Validate synchronization across Python, gateway, and TS frontend for correct autocomplete, execution, and config behavior.
  • Use when commands don't appear in autocomplete, don't execute, or behave differently across layers.

Quick Start

Run the debugging workflow to diagnose a failing Hermes TUI slash command.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why do my Hermes TUI slash commands not appear in autocomplete or execute inconsistently?

Inconsistent slash commands occur when the Python COMMAND_REGISTRY, gateway dispatch, and Ink frontend handlers are out of sync. You must investigate command presence across these three layers to ensure autocomplete and execution behave consistently.

How do I debug a missing slash command across Python, gateway, and TypeScript frontend layers?

Debug missing commands by validating synchronization across the Python backend, gateway dispatch, and Ink frontend. Check that the command exists in the COMMAND_REGISTRY, is known to the gateway, and has matching TypeScript slash handlers.

When do I need to synchronize slash commands across the Python CLI, gateway, and Ink UI?

Synchronize slash commands when adding new commands, updating existing ones during development, or observing different behaviors across the CLI, gateway, and UI. This alignment ensures correct autocomplete, execution, and config behavior.

What is the best way to fix a misregistered slash command in a TypeScript and Python TUI application?

The best way is to run a debugging workflow that checks alignment between the Python COMMAND_REGISTRY, the gateway command dispatch, and the Ink TypeScript frontend slash handlers to resolve execution and autocomplete inconsistencies.

How do I ensure new Hermes TUI commands are correctly registered for autocomplete and execution?

Ensure correct registration by validating command presence in the Python COMMAND_REGISTRY, confirming the gateway knows the command, and adding matching slash handlers in the Ink TypeScript frontend for proper autocomplete and execution.