debug

Automate structured debugging workflows for backend/CLI and frontend/UI issues.

Updated Jul 10, 2022
One-click install
npx skills add https://github.com/samuerio/.dotfiles --skill debug-samuerio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/samuerio/.dotfiles/tree/main/agents/skills/debug
Command: npx skills add https://github.com/samuerio/.dotfiles --skill debug-samuerio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex software stacks by executing structured workflows across backend/CLI and frontend/UI components, ensuring reproducibility and clear validation trails.

Core Features & Use Cases

  • Orchestrates debugging sessions in tmux for services and CLI tools.
  • Enables browser-facing issue reproduction with chrome-devtools MCP.
  • Produces a final diagnostic report detailing startup targets, steps taken, and results.

Quick Start

Load the tmux-based debug workflow and attach to the target service session to begin debugging.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug runtime failures across both frontend and backend environments?

Debugging runtime failures across frontend and backend environments requires a structured workflow that reproduces issues, inspects logs, and validates fixes. This Skill automates that process for server-side services and client-side interfaces.

What's the best way to reproduce UI issues in a browser during a debugging session?

Reproducing UI issues in a browser is handled through chrome-devtools MCP integration. This enables browser-facing issue reproduction while orchestrating the overall debugging workflow within a tmux session.

Do I need tmux to start debugging CLI and backend services?

Yes, tmux is required to start debugging CLI and backend services. The workflow orchestrates debugging sessions by attaching to target service sessions managed within a tmux environment.

How does structured debugging validate fixes for client-side interfaces?

Structured debugging validates fixes by producing a final diagnostic report. This report details startup targets, steps taken during the session, and validation results across both client-side interfaces and server-side services.

Can I inspect server-side logs while reproducing frontend issues simultaneously?

Yes, you can inspect server-side logs while reproducing frontend issues. The workflow operates across backend/CLI and frontend/UI components simultaneously, orchestrating tmux sessions for services and chrome-devtools for browser contexts.

What limitations exist when debugging complex software stacks with structured workflows?

Limitations include the strict dependency on loading the tmux skill first and using chrome-devtools MCP for browser contexts. Debugging complex software stacks outside these integrated session environments is not supported by this workflow.