debugging-zedclaw-tui-commands

Reconcile ZedClaw TUI slash-command definitions across Python registry, gateway, and Ink handlers.

4|Updated May 18, 2026

Search Tags:#typescript #python #slash commands #command registry #tui debugging #zedclaw #gateway dispatch

Ready to run

npx skills add https://github.com/ZardLi1115/zedclaw --skill debugging-zedclaw-tui-commands

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging-zedclaw-tui-commands
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/software-development/debugging-zedclaw-tui-commands
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill debugging-zedclaw-tui-commands

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes ZedClaw TUI slash-command bugs caused by mismatches between the Python command registry, the gateway dispatch layer, and the Ink/TypeScript frontend.

Core Features & Use Cases

Diagnose cross-layer command drift: Determines whether a command is missing, mis-registered, or inconsistently handled across Python, gateway, and UI.
Restore autocomplete correctness: Ensures command definitions in the Python COMMAND_REGISTRY propagate to the TUI autocomplete data.
Align dispatch and live UI behavior: Verifies gateway dispatch routing and confirms TUI state updates occur immediately rather than only persisting config.

Quick Start

Ask the skill to debug a specific failing slash command by checking whether it exists in the Ink frontend handlers, the TUI autocomplete registry, and the Python and gateway dispatch paths for that canonical command name.

Frequently Asked Questions about debugging-zedclaw-tui-commands

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

FAQPage Schema

Why do my ZedClaw TUI slash commands work in the CLI but fail in the frontend interface?▼

TUI slash commands fail across interfaces due to mismatches between the Python command registry, gateway dispatch, and Ink TypeScript frontend. Resolving this requires validating COMMAND_REGISTRY entries, ensuring gateway dispatch alignment, and verifying local handler state propagation.

How do I fix ZedClaw slash commands missing from the TUI autocomplete?▼

To restore TUI autocomplete correctness, you must ensure command definitions in the Python COMMAND_REGISTRY propagate properly to the frontend autocomplete data. This involves checking cross-layer command drift between the backend registry and Ink UI logic.

What causes ZedClaw TUI state updates to persist in config but not reflect immediately in the UI?▼

Live UI behavior fails to update when gateway dispatch routing and Ink TypeScript local handler state propagation are misaligned. You must verify gateway dispatch routing and confirm TUI state updates occur immediately rather than only persisting config.

How do I debug a failing ZedClaw slash command across backend and frontend layers?▼

Debug a failing slash command by checking its canonical name against Ink frontend handlers, the TUI autocomplete registry, and Python and gateway dispatch paths. This diagnoses whether the command is missing, mis-registered, or inconsistently handled.

Do I need TypeScript and Python environments to fix ZedClaw command registry issues?▼

Yes, fixing ZedClaw TUI slash-command bugs requires validating Python COMMAND_REGISTRY entries and verifying Ink TypeScript local handler behavior. You must reconcile command definitions and handlers across both backend and frontend layers.

What are the limitations when debugging ZedClaw command drift between gateway dispatch and UI?▼

Debugging command drift is limited to scenarios where commands are missing from autocomplete, work in CLI but not TUI, or update persisted config without live UI changes. It requires validating Python registry, gateway dispatch, and TypeScript handler alignment.