debug

Diagnose service failures by inspecting logs and system states with Bash.

3|1|Updated Apr 19, 2024
One-click install
npx skills add https://github.com/guccang/blogclaw --skill debug-guccang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/guccang/blogclaw/tree/main/cmd/llm-agent/workspace/skills/debug
Command: npx skills add https://github.com/guccang/blogclaw --skill debug-guccang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify the root causes of service failures, errors, process issues, and operational problems by guiding systematic investigation instead of guessing.

Core Features & Use Cases

  • Log Investigation: Guides targeted log inspection using recent entries, error keywords, and time-based filtering.
  • System State Checks: Helps inspect processes, ports, files, permissions, and related runtime conditions with Bash.
  • Use Case: When a production API returns errors, use this Skill to review relevant logs, identify the failure cause, and determine appropriate fixes.

Quick Start

Ask the debug skill to investigate the service error by checking the relevant logs and system status.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug service failures using system logs and Bash?

Debug service failures by using Bash workflows to inspect recent log entries, filter by error keywords, and validate system states. This approach collects focused evidence to support root cause analysis before any remediation is attempted.

What is the best way to diagnose application outages and port conflicts?

Diagnose application outages and port conflicts through structured investigation of system states. This involves checking running processes, validating port usage, and inspecting runtime conditions with Bash commands to pinpoint the failure.

How does structured error analysis help troubleshoot production API errors?

Structured error analysis troubleshoots production API errors by guiding targeted log inspection and system state checks. It replaces guessing with systematic evidence collection to identify the exact failure cause and determine appropriate fixes.

Can I use this method to investigate process failures on my server?

Yes, you can investigate server process failures by applying Bash-based inspection workflows. These workflows validate target processes, collect operational evidence, and inspect related runtime conditions to support root cause analysis.

When should I use a systematic debugging workflow instead of guessing?

Use a systematic debugging workflow when facing service failures, interface errors, or operational problems. It ensures you validate targets and collect evidence through log investigation and system state checks before attempting fixes.

What do I need to check before diagnosing operational errors and interface failures?

Before diagnosing operational errors and interface failures, ensure you have Bash access to inspect system states. You need to check relevant logs, running processes, file permissions, and port conflicts to gather evidence for root cause analysis.