skills.rest
SatangThevalue
SatangThevalueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging-hermes-tui-commands

Debug Hermes TUI slash commands across Python CLI, gateway, and Ink frontend.

Updated Jun 1, 2026
Search Tags:#typescript#debugging#python#tui#slash-commands#hermes
One-click install
npx skills add https://github.com/SatangThevalue/ai-skills --skill debugging-hermes-tui-commands-satangthevalue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-hermes-tui-commands
Source: https://github.com/SatangThevalue/ai-skills/tree/main/skills/software-development/debugging-hermes-tui-commands
Command: npx skills add https://github.com/SatangThevalue/ai-skills --skill debugging-hermes-tui-commands-satangthevalue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps identify and fix cross-layer issues in Hermes TUI slash commands, spanning Python CLI, gateway, and Ink frontend, when behavior is inconsistent or missing from UI.

Core Features & Use Cases

  • Cross-layer debugging workflow for slash commands across Python, gateway, and UI.
  • Step-by-step investigation to confirm registry definitions, gateway dispatch, and frontend handlers.
  • Use Case: A developer encounters a command that appears in the TUI but not in autocomplete and needs to align Python registry, gateway routes, and Ink handlers.

Quick Start

Run Hermes in TUI mode and reproduce the failing slash command to start the debugging session.

Frequently Asked Questions about debugging-hermes-tui-commands

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

FAQPage Schema
How do I debug Hermes TUI slash commands that work in CLI but not in the UI?▼

Debugging Hermes TUI slash commands involves inspecting the canonical COMMAND_REGISTRY in hermes_cli/commands.py, validating gateway dispatch paths, and verifying frontend slash handling in ui-tui to resolve cross-layer inconsistencies.

Why are slash commands missing from autocomplete in my Ink frontend TUI?▼

Slash commands missing from autocomplete typically indicate a disconnect between the Python CLI registry, gateway routes, and Ink frontend handlers, requiring end-to-end cross-layer debugging to align all three layers.

What is the correct workflow to debug slash commands across Python, gateway, and Ink layers?▼

The correct workflow starts by running Hermes in TUI mode to reproduce the failing command, then step-by-step investigating registry definitions, gateway dispatch paths, and frontend handlers to ensure consistent behavior.

Can I use this debugging workflow for slash command issues across staging and production environments?▼

Yes, the cross-layer debugging workflow applies to slash command misbehavior across development, staging, and production workflows, ensuring the UI reflects live state consistently in each environment.

What should I check first when a Hermes TUI slash command does not reflect live state in the UI?▼

When a slash command does not reflect live state, first inspect the canonical COMMAND_REGISTRY in hermes_cli/commands.py to confirm definitions before validating the gateway dispatch and Ink frontend handlers.

Related Skills

Explore More Software Engineering Skills→
zengbaochengzengbaocheng

debugging-hermes-tui-commands

Inspect Python command registry, gateway router, and Ink frontend to fix Hermes TUI slash commands.

Community
Advanced
devMoezdevMoez
1

debugging-Titan-tui-commands

Align Python command registry, TUI gateway routing, and Ink/TypeScript slash handlers.

Community
Intermediate
DarkArty07DarkArty07
3

debugging-hermes-tui-commands

Diagnose cross-layer Hermes TUI slash command synchronization bugs across Python, JSON-RPC, and Ink.

Community
Intermediate
Monjyu1101Monjyu1101
1

debugging-hermes-tui-commands

Debug Hermes TUI slash command misalignment across Python, gateway, and Ink frontends.

Community
Advanced