skills.rest
ps-carvalho
ps-carvalhoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Analyze logs, stack traces, and git history to identify software defect root causes.

Updated Mar 12, 2026
Search Tags:#debugging#troubleshooting#root cause analysis#log analysis#diagnostics#error analysis
One-click install
npx skills add https://github.com/ps-carvalho/spavn-agents --skill debug-ps-carvalho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ps-carvalho/spavn-agents/tree/main/.opencode/skills/debug
Command: npx skills add https://github.com/ps-carvalho/spavn-agents --skill debug-ps-carvalho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides deep troubleshooting and root cause analysis for software issues, helping developers quickly understand and resolve bugs without directly modifying code.

Core Features & Use Cases

  • Root Cause Analysis: Identifies the fundamental reason behind errors or unexpected behavior.
  • Log and Trace Analysis: Examines error messages, stack traces, and logs to pinpoint issues.
  • Use Case: When a critical bug is reported in production, this Skill can analyze the provided error logs and stack traces to identify the exact line of code and the logical flaw causing the problem.

Quick Start

Use the debug skill to analyze the provided error logs and stack trace for the recent login failure.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I perform root cause analysis for a software defect?▼

Root cause analysis identifies the fundamental reason behind software defects by examining execution flow, git history, and error messages to pinpoint the exact logical flaw without modifying code.

What is the best way to troubleshoot errors using stack traces and logs?▼

Troubleshooting with stack traces and logs involves analyzing error messages and execution flow to pinpoint the exact line of code and the logical flaw causing unexpected software behavior.

Can I use this to analyze a critical bug reported in production?▼

Yes, you can analyze a critical bug reported in production by providing the relevant error logs and stack traces to identify the exact source of the issue.

Does this debugging process directly modify my source code?▼

No, this debugging process identifies the source of issues by analyzing execution flow and error messages without directly modifying your source code.

When do I need to analyze git history for error diagnostics?▼

Analyzing git history for error diagnostics is needed when investigating recent changes to identify the fundamental reason behind errors or unexpected software behavior.

Why does analyzing execution flow help with software troubleshooting?▼

Analyzing execution flow helps with software troubleshooting by mapping how the application reached an error state, enabling precise identification of the logical flaw causing the defect.

Related Skills

Explore More Software Engineering Skills→
koralliskorallis
90

root-cause-tracing

Traces bugs backward through call stacks and execution flows to pinpoint their source.

Community
Advanced
MrHadiSatrioMrHadiSatrio

fixing-defects

Reproduce, isolate, and fix software defects with regression tests and Git commits.

Community
Intermediate
ppiankovppiankov

logtap

Captures, triages, and analyzes ephemeral Kubernetes logs in real-time via CLI and sidecar injection.

Community
Advanced
kfolkeskfolkes
2

bandit-security-scan

Scan Python source code for security vulnerabilities using the Bandit linter.

Community
Intermediate