debugging-hermes-tui-commands

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

3|1|Updated Apr 19, 2024
One-click install
npx skills add https://github.com/guccang/blogclaw --skill debugging-hermes-tui-commands-guccang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/guccang/blogclaw/tree/main/cmd/hermes-agent/vendor/hermes_runtime/skills/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/guccang/blogclaw --skill debugging-hermes-tui-commands-guccang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve broken Hermes TUI slash commands caused by inconsistencies between Python command registration, gateway routing, and the TypeScript interface.

Core Features & Use Cases

  • Cross-Layer Debugging: Trace command behavior across the Python backend, tui_gateway bridge, and Ink frontend.
  • Command Repair Guidance: Identify missing registrations, autocomplete problems, dispatch failures, and state synchronization issues.
  • Use Case: When a slash command appears in one interface but fails in another, use this Skill to locate the mismatched layer and apply the appropriate fix.

Quick Start

Ask the skill to debug why a Hermes TUI slash command is missing from autocomplete or behaving differently between CLI and TUI.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
Why does my Hermes TUI slash command fail in the frontend but work in the CLI?

Slash command failures across interfaces indicate a mismatch between the Python command registry, gateway dispatch, and TypeScript Ink frontend handlers. Tracing command behavior across these three layers locates the specific routing or state synchronization issue causing the inconsistency.

How do I debug a missing slash command in Hermes TUI autocomplete?

To debug missing slash command autocomplete issues, verify the Python command registration, check the JSON-RPC gateway communication routing, and inspect the TypeScript Ink interface for state update failures. Cross-layer verification identifies the unregistered or undispatched command.

What causes slash command dispatch failures in a TypeScript Ink and Python gateway architecture?

Dispatch failures stem from inconsistencies between Python command definitions, JSON-RPC gateway routing logic, and TypeScript Ink frontend handlers. Coordinated verification of command registries and routing logic exposes the architectural mismatch preventing successful command execution.

Can I fix Hermes TUI state synchronization issues without rebuilding the entire project?

Yes, targeted debugging identifies the specific mismatched layer between the Python backend, gateway bridge, and Ink frontend. Isolating the command definition or routing logic error allows precise repairs, though rebuild testing workflows are required to verify the fix.

When do I need to trace command behavior across Python, gateway, and TypeScript layers?

Cross-layer tracing is necessary when a slash command appears in one interface but fails in another, or when autocomplete behaves differently between CLI and TUI. This indicates a broken command registration, gateway dispatch, or frontend handler synchronization.

What is the best way to resolve JSON-RPC gateway routing mismatches for Hermes Agent commands?

The best way to resolve gateway routing mismatches is cross-layer debugging, which traces command behavior from the Python CLI backend through the JSON-RPC gateway to the TypeScript Ink interface to identify and repair the exact dispatch failure point.