debugging-hermes-tui-commands

Trace Hermes TUI slash command failures across Python, JSON-RPC, and TypeScript layers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers diagnose and resolve Hermes TUI slash command failures caused by mismatches between Python command registration, gateway dispatch, and Ink frontend behavior.

Core Features & Use Cases

  • Cross-layer debugging: Trace slash commands across the Python backend, JSON-RPC gateway, and TypeScript TUI frontend.
  • Command synchronization checks: Identify missing autocomplete entries, broken dispatch paths, and inconsistent CLI versus TUI implementations.
  • Live UI troubleshooting: Resolve cases where configuration changes persist but do not immediately update the running TUI experience.

Quick Start

Use the debugging-hermes-tui-commands skill to investigate why a Hermes TUI slash command is missing from autocomplete or behaving incorrectly.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why are my Hermes TUI slash commands missing from autocomplete?

Hermes TUI slash command autocomplete failures often stem from mismatches between Python backend registration and the TypeScript frontend. Cross-layer debugging traces these definitions through the JSON-RPC gateway to identify missing entries and broken dispatch paths.

How do I debug slash commands across a Python backend and TypeScript TUI?

Debugging slash commands across a Python backend and TypeScript TUI requires inspecting JSON-RPC routing and frontend handlers. Coordinated checks identify inconsistent CLI versus TUI implementations and verify gateway dispatch behavior.

How to fix Hermes TUI configuration changes that do not update the live UI?

Live UI troubleshooting for Hermes TUI resolves cases where configuration changes persist but do not immediately update the running interface. It inspects frontend handlers and rebuild verification workflows to restore live state updates.

What causes inconsistent slash command behavior between the Hermes CLI and TUI?

Inconsistent slash command behavior between the Hermes CLI and TUI is caused by desynchronized Python command definitions and gateway dispatch paths. Command synchronization checks identify broken routes and resolve the mismatches.

Does adding a new Hermes TUI command require rebuilding the TypeScript frontend?

Adding a new Hermes TUI command requires rebuild verification workflows to ensure the TypeScript frontend recognizes the Python backend registration. This confirms the JSON-RPC routing and Ink handlers are correctly synchronized.